DPascalBernard / maven-alfresco-archetypes

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

Remove enforcer for the upcoming Alfresco Enterprise 4.1.2 #106

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Alfresco Enterprise 4.1.2 will come with full dependencies in published pom 
files (see https://issues.alfresco.com/jira/browse/ALF-16648)
This means that one will be able to use the SDK with it... except that there is 
a call to the enforcer plugin that prevents it!

The SDK should
* Stop enforcing Java 7 (Alfresco 4.1 is supported on JDK 6)
* Stop enforcing the Alfresco version to be 4.2+. 
I suggest the following regexp instead: ^(4\.1\.[2-9]|4\.[2-9]|[5-9]).*
(meaning: 4.1.2+, 4.2+ or 5+)

Thanks!

Original issue reported on code.google.com by samuel.l...@alfresco.com on 19 Dec 2012 at 6:15

GoogleCodeExporter commented 8 years ago
Or better update to include 4.1.2 ... assigned to the regexp guru :)

Original comment by colum...@gmail.com on 24 Jan 2013 at 5:26

GoogleCodeExporter commented 8 years ago

Original comment by colum...@gmail.com on 24 Jan 2013 at 5:26

GoogleCodeExporter commented 8 years ago

Original comment by samuel.l...@alfresco.com on 31 Jan 2013 at 6:25

GoogleCodeExporter commented 8 years ago
Is the 1.1-SNAPSHOT going to be updated soon? I am trying to use Enterprise 
4.1.2 with this SDK. I updated my POM to point to alfresco-sdk-parent 
1.1-SNAPSHOT, but it is not seeing this change:

[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-sdk-requirements) @ 
ccms ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireProperty failed with 
message:
Property "alfresco.version" evaluates to "4.1.2".  This does not match the 
regular expression "^(4\.[2-9]|[5-9]).*"
[WARNING] Rule 2: org.apache.maven.plugins.enforcer.RequireJavaVersion failed 
with message:
As the SDK works only with Alfresco 4.2+, and Alfresco 4.2+ requires Java 7, 
you need Java 7

Original comment by tonyapu...@gmail.com on 6 Feb 2013 at 12:12

GoogleCodeExporter commented 8 years ago
Hi Tony,

I've just deployed a new 1.1-SNAPSHOT.

Can you let us know if that works for you?

Original comment by ray.ga...@alfresco.com on 6 Feb 2013 at 1:48

GoogleCodeExporter commented 8 years ago
Based on instructions from Alfresco Support, I had removed from my pom.xml 
repository references to
https://artifacts.alfresco.com/nexus/content/groups/public
https://artifacts.alfresco.com/nexus/content/groups/public-snapshots

In favor of only having
https://artifacts.alfresco.com/nexus/content/groups/private

However, the private repo seemingly doesn't have the latest snapshots so I was 
picking up the old, previously cached 1.1-SNAPSHOT. I deleted org/alfresco from 
my local maven cache and then added those 2 repositories back into my pom.xml, 
then I was able pull down the updated 1.1-SNAPSHOT as well as the 4.1.2 
enterprise artifacts.

The 1.0 all-in-one archetype sets snapshot update policy to "never" for the 
snapshots repository. Seems like that should default to "daily" unless there is 
a confounding factor.

I was able to get jetty to start on the all-in-one archetype with 4.1.2.

Thank you for your help!

Original comment by tonyapu...@gmail.com on 6 Feb 2013 at 3:58

GoogleCodeExporter commented 8 years ago
Great to hear you've got things working.

Would you mind raising a separate issue on the snapshot update policy?

Original comment by ray.ga...@alfresco.com on 6 Feb 2013 at 6:39