it's not exactly useful in the context of plugging the sources into the IDE. The goal will just zip the project directory. java sources don't show up at the root of the zip but somehwere down the structure, like in src/java folder. And besides that, if your project pom extends some other POM, the parent definitions won't make it into the distribution zip. -> it can happen that sources will not be buildable anyway, because the pom misses dependencies, or resources.
Milos On 4/15/05, Mykel Alvis <[EMAIL PROTECTED]> wrote: > If you're talking about a source zip for your own project, it's the > dist plugin. like > maven dist:deploy-src > > > On 4/14/05, Alex Soto <[EMAIL PROTECTED]> wrote: > > The integration of the src zip is cool, but I ended up tracking down > > the source zip myself from the projects website or generating myself. > > I haven't found how to 'create' one. > > > > On 4/14/05, Milos Kleint <[EMAIL PROTECTED]> wrote: > > > I didn't know about this eclipse plugin property, but there's > > > definitely no official plugin/goal for it. I assume your zip is > > > expected to contain the package rooted hierarchy of sources, correct? > > > I needed something like that for netbeans as well and submitted a > > > patch to maven-dist-plugin > > > http://jira.codehaus.org/browse/MPDIST-21 > > > however that one doesn't crete zip but jar and places it under > > > {groupid}/src.jars directory. That's similar to the way javadocs are > > > stored in the repository. > > > > > > Until it gets integrated into the dist plugin (i hope it will), I've > > > placed the goals to generate/install/upload the source zips into my > > > maven plugin at > > > http://www.ibiblio.org/maven/mevenide/plugins/maven-mevenide-plugin-0.3.jar > > > goals are: mevenide:src-distribution, > > > mevenide:src-distribution-install, mevenide:src-distribution-deploy > > > > > > Hope that helps. > > > > > > Milos Kleint > > > > > > On 4/14/05, Damien Raude-Morvan <[EMAIL PROTECTED]> wrote: > > > > Hello all, > > > > > > > > I'm trying to get maven-eclipse-plugin generating, in addition of the > > > > classpath entries, sourcepath references (to a source zip file or > > > > directly to source folder of the dependencies). > > > > > > > > I've seen on the maven-eclipse-plugin website that it will check for a > > > > file src/{artifactId}-${version}.zip in local maven repository (and > > > > having a quick look at Jelly code seems confirm that :) > > > > > > > > But what goal should I call to get maven generating this .zip file ? > > > > > > > > Any advices ? > > > > > > > > [1] http://maven.apache.org/reference/plugins/eclipse/ > > > > > > > > -- > > > > Damien Raude-Morvan > > > > Movalys / www.movalys.com > > > > Adeuza / www.adeuza.fr > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
