You can put your libs into Nexus without 'mavenizing' them.
Lot less to do ...
Wolfgang
-Ursprüngliche Nachricht-
Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Gesendet: Donnerstag, 29. September 2011 11:09
An: Maven Users List
Betreff: Re: Using Maven with custom
Maybe http://maven.apache.org/enforcer/enforcer-rules/index.html
could help.
Wolfgang
-Ursprüngliche Nachricht-
Von: Jörg Schaible [mailto:joerg.schai...@scalaris.com]
Gesendet: Mittwoch, 13. April 2011 11:55
An: users@maven.apache.org
Betreff: Re: breaking backwards compatibility
Hi
Maybe this plugin would help:
http://mojo.codehaus.org/versions-maven-plugin/
W.
-Ursprüngliche Nachricht-
Von: C. Benson Manica [mailto:cbman...@gmail.com]
Gesendet: Donnerstag, 26. August 2010 17:23
An: Maven Users List
Betreff: Change development version
What is the proper way to
Hi everybody!
Just imagine we had a profiles definition in a pom.xml such as
profile group=database type=manditory
idMySQL/id
... as we know it ...
/profile
profile group=database type=manditory
idOracle/id
... as we know it ...
/profile
profile
Hello
here is the source of an example how we (my friend and Apple-Fan Michael and
myself) did do it some months ago last year.
The purpose was to collect log4j configuration from various locations into one
file.
The idea is to include the dtd and the xsl script in the jar, to be
Hello,
did you make sure, that in the MAVEN settings.xml or your pom.xml, there is a
correct entry for the pax/OSGI repositories ?
AFAIK, they are NOT the standard Maven repo.
Wolfgang
-Ursprüngliche Nachricht-
Von: Fotis Paraskevopoulos [mailto:for...@existanze.com]
Gesendet: Montag,
, Schrecker, Wolfgang wrote:
Hello,
did you make sure, that in the MAVEN settings.xml or your pom.xml,
there is a correct entry for the pax/OSGI repositories ?
AFAIK, they are NOT the standard Maven repo.
Wolfgang
-Ursprüngliche Nachricht-
Von: Fotis Paraskevopoulos [mailto:for
some comments inline.
On Aug 24, 2009, at 12:22 , Schrecker, Wolfgang wrote:
Nowhere, Fotis,
because it has nothing to do with with eclipse:eclipse. It concerns
Maven.
When your pom.xml is fine, eclipse:eclipse will tell eclipse so.
My pom is fine, since I can, from the command line
