Question re. the Maven scm-plugin:
* http://maven.apache.org/scm/plugins/usage.html
*
Example, in pom.xml:
scm:svn:http://somerepository.com/svn_repo/trunk
scm:svn:https://somerepository.com/svn_repo/trunk
http://somerepository.com/view.cvs
*What exactly is the tag used fo
> > I've refactored my ant-based library into maven based one, but I've
> > encounter the same issue reported as the blocker here:
> > http://jira.codehaus.org/browse/MSHARED-182
> This is actually a plexus-archiver issue.
> I noticed they're using lowercased names for the keys
> I don't know abou
This is actually a plexus-archiver issue.
I noticed they're using lowercased names for the keys
I don't know about such spec of manifest entries, but I guess they had a reason
for it.
Try also Jira[1] or GIT[2] to get more info.
-Robert
[1] http://jira.codehaus.org/browse/PLXCOMP/component/1
hi all
i have successfully ran the FolderRunner from my maven project with this
configuration
org.codehaus.mojo
exec-maven-plugin
1.1.1
integration-tes
This is a recurring discussion. Almost everyone has this problem in one
form or another.
IMO the best thing to do is to remove all deployment stuff from development.
In general, deployment configuration is the responsibility of the system
administrator not the developer.
http://blog.artifact-
Hello Everyone,
I've refactored my ant-based library into maven based one, but I've
encounter the same issue reported as the blocker here:
http://jira.codehaus.org/browse/MSHARED-182
Seeing the date of creation of this ticket I suppose there is no prospect of
quick fix in the near future.
Is ther
Greetings,
On Fri, Nov 18, 2011 at 11:17 AM, Heck, Timo wrote:
> After a while I figured out that maven does package libs which
> should not be there.
> There are multiple versions of some libs which actually are resolved
> once in pom
> but there are also libs which are not defined at all.
Mayb
> I get strange errors.
Could you be more specific? Some actual error messages would be great.
>
> After a while I figured out that maven does package libs which
> should not be there.
Be concrete: which libs? What makes you believe they should not be there?
> There are multiple versions of som