directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Seelmann <seelm...@apache.org>
Subject [ApacheDS] maven-source-plugin and maven-jar-plugin
Date Fri, 04 Jun 2010 15:58:11 GMT
Hi dev,

the following POMs define the maven-source-plugin and create a source
jar during a local build:

apacheds/http-integration/pom.xml
apacheds/core-api/pom.xml
apacheds/protocol-shared/pom.xml
apacheds/xbean-spring/pom.xml
apacheds/core/pom.xml
apacheds/protocol-changepw/pom.xml
apacheds/syncrepl/pom.xml
apacheds/protocol-ntp/pom.xml
apacheds/core-jndi/pom.xml
apacheds/protocol-dns/pom.xml
apacheds/server-jndi/pom.xml
apacheds/kerberos-test/pom.xml
apacheds/ldif-partition/pom.xml
apacheds/jdbm-partition/pom.xml
apacheds/protocol-ldap/pom.xml
apacheds/interceptor-kerberos/pom.xml
apacheds/protocol-kerberos/pom.xml
apacheds/jdbm-store/pom.xml

Additional in project/pom.xml the maven-source-plugin is defined in two
profiles: release and full.

So the source jars are generated and deployed during the release, that
is required, so far so good.

My questions:

What is the "full" profile used for?

Can we remove the definiton of the maven-source-plugin from all the POMs
listed above? I think during the local build those are not requried.

Kind Regards,
Stefan

Mime
View raw message