Hi Ahmet,

You should always create tickets for each distinct issue you have
found.  You are then free to commit a fix for the ticket, on your own
judgment, or attach a patch and let others review it.  It is up to you
based on the situation and how confident you are about the fix.

Please also make sure that when you commit a fix with a related
ticket, you commit an entry in CHANGES.txt so we can track what has
occurred.

Thanks!
Karl



On Mon, Sep 3, 2012 at 7:25 PM, Ahmet Arslan <[email protected]> wrote:
> Hello all,
>
> 1) "mvn -Dmaven.test.skip=true clean install" fails on trunk giving following 
> exception:
>
> Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:2.3:unpack-dependencies 
> (unpack-amps) on project mcf-alfresco-war-test: Execution unpack-amps of goal 
> org.apache.maven.plugins:maven-dependency-plugin:2.3:unpack-dependencies 
> failed: Unable to load the mojo 'unpack-dependencies' in the plugin 
> 'org.apache.maven.plugins:maven-dependency-plugin:2.3'. A required class is 
> missing: org/codehaus/plexus/archiver/ArchiverException
> [ERROR] -----------------------------------------------------
> [ERROR] realm =    plugin>org.apache.maven.plugins:maven-dependency-plugin:2.3
>
> When I remove <version>2.3</version> from maven-dependency-plugin all works. 
> I checked other pom.xml files, they don't have version tag.
>
> 2) I see some connectors (sharepoint, documentum, livelink, memex, meridio, 
> filenet) do not have pom.xml files. (I have one handy for sharepoint that 
> passes mvn package/install) Is this because they are proprietary connectors?
>
> For 1) and sharepoint pom.xml, should I file a jira or Can I commit directly?
>
> Thanks,
> Ahmet

Reply via email to