search

DPascalBernard / maven-alfresco-archetypes

Automatically exported from code.google.com/p/maven-alfresco-archetypes
0 stars 0 forks source link

Deprecate use of classifier "community" and "enterprise" for Alfresco artifacts and embed that in version numbers #62

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Right now classifiers (which typically should be used to differentiate multiple 
artifacts produced of the same build, e.g. artifactId-test.jar, 
artifactId-javadoc.jar) are abused in the Alfresco Maven artifacts naming since 
a classifier is used to express the alfresco.edition, i.e. "community" or 
"enterprise".

This prevents to actually use classifier for what they are meant for, i.e. to 
also deploy javadoc or source packages.

I propose that archetypes are aligned on the following POM properties:

alfresco.edition=[community,enterprise]
alfresco.version.number=3.4.e
alfresco.version.label=${alfresco.version.number}-${alfresco.edition}

This I will deploy artifacts with a version which already embeds a number and 
an edition (-Dversion=${alfresco.version.label} and archetypes will refer only 
to specific versions (no more classifiers), e.g.:

        <dependency>
            <groupId>org.alfresco</groupId>
            <artifactId>alfresco</artifactId>
            <version>${alfresco.version.label}</version>
            <type>war</type>
        </dependency>

WDYT? Seems much cleaner to me.

Original issue reported on code.google.com by colum...@gmail.com on 16 Nov 2011 at 4:52

GoogleCodeExporter commented 9 years ago 
Hi Gabriele,

I would suggest first put the edition and the the version.

Doing that way you can still use maven trick to get the latest version...

Example: <version>[enterprise-4.0,<version>

Not sure 100% about maven syntax (im to lazy to search) but the idea is there.

Original comment by steph...@clinckart.com on 17 Nov 2011 at 5:17

GoogleCodeExporter commented 9 years ago 
As per https://issues.alfresco.com/jira/browse/ALF-11027, we have changed the 
approach here.

For now we dropped both classifier and version manipulation, but using groupId 
to distinguish Community and Enterprise releases.

In particular as per 
http://wiki.alfresco.com/wiki/Alfresco_Artifacts_Repository, we have:

org.alfresco --> Alfresco Community artifacts
org.alfresco.enterprise --> Alfresco Enterprise artifacts

Solving this issue as part of the Maven Alfresco SDK 1.0.

Original comment by colum...@gmail.com on 29 Oct 2012 at 11:11