Sounds useful. I just don't know how...
Not too familiar with all the build systems as you might have gathered...

Op 10 apr. 2014, om 17:50 heeft Andrew Phillips <notifications@github.com<mailto:notifications@github.com>> het volgende geschreven:


In deployit-udm-plugins/utility-plugins/dartransfer-plugin/pom.xml:

> +                     <groupId>com.xebialabs.deployit.plugins</groupId>
> +                     <artifactId>remoting-plugin</artifactId>
> +                     <version>3.9.4</version>
> +             </dependency>
> +             <dependency>
> +                     <groupId>com.xebialabs.overthere</groupId>
> +                     <artifactId>overthere</artifactId>
> +                     <version>2.3.0</version>
> +             </dependency>
> +             <dependency>
> +                     <groupId>org.apache.httpcomponents</groupId>
> +                     <artifactId>httpmime</artifactId>
> +                     <version>4.3.2</version>
> +             </dependency>
> +     </dependencies>
> +     <!-- <build> <pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId>


When active it compiles the jar with another default class that allows the jar to be used standalone.

That certainly sounds useful, but would it then make more sense to wrap it in a Maven profile?

—
Reply to this email directly or view it on GitHub<https://github.com/xebialabs/community-plugins/pull/58/files#r11491602>.