Michael McCallum <[EMAIL PROTECTED]> wrote on 03/07/2008 14:05:09:
> 11) don't mix inheritance and aggregation. that means a parent pom NEVER
ever
> has modules, if you think about the concept for a minute - or longer -
there
> will be a moment of enlightenment
Sorry for jumping in here, but
Hi Peter,
Peter Horlock wrote:
> Okay,
>
> one last thing - this conversation has helped me a LOT
> already, but, to
> catch it all, I need some more:
>
> 1) You say your version ranges wouldn't break a build - but what about
> transitive dependencies that these new versions might have (in case
Are there any maven plugins that can load dependencies from user libraries of
eclipse? thanx.
--
View this message in context:
http://www.nabble.com/Any-maven-plugin-can-load-dependencies-from-eclipse-user-libraries--tp18273625p18273625.html
Sent from the Maven - Users mailing list archive at Na
Okay,
one last thing - this conversation has helped me a LOT already, but, to
catch it all, I need some more:
1) You say your version ranges wouldn't break a build - but what about
transitive dependencies that these new versions might have (in case they are
overwriting depd. mgmt for example)? Wh
On Fri, Jul 4, 2008 at 4:49 AM, Rakesh Sinha <[EMAIL PROTECTED]> wrote:
> Does this mean if it would be the job of eclipse team to publish the
> .pom files to the repository. Is there any way any other individual
> contributor can contribute to this ?
It means the latter. You can create a bundle
Mikel Cármenes Cavia wrote:
That makes pretty good sense.
Good to hear :-)
So, from what I understand, you do keep your jar dependencies in a lib
folder or some other sort of external storage, correct?
Yes, that's correct. That's a manual process, though because we never
had the need to au
Hi,
When i try manve test, it throws error saying "Error creating properties
files for forking; nested exception is java.io.IOException: The system
cannot find the path specified" in windows 2003 machine, could you please
help me.
[INFO] Surefire report directory:
C:\p4_ws\Mercury\ML\imf\qatests\
Does this mean if it would be the job of eclipse team to publish the
.pom files to the repository. Is there any way any other individual
contributor can contribute to this ?
On 7/3/08, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 3, 2008 at 3:43 AM, Rakesh Sinha <[EMAIL PROTECTED]> wr
Realistically, you should be talking to the people responsible for the
tutorial. They know a lot more about their specific code/project than
anyone on this list, and would probably appreciate someone reporting
an issue with their documentation so they can resolve it.
Wayne
On 7/3/08, fx5900 <[EMA
i don't think plugin resolution supports ranges, the brackets are implied for
plugins in that they are all strict versions.
i've have go back and read the code again...
On Fri, 04 Jul 2008 03:12:35 André Kelpe wrote:
> Hi Jan!
>
> > I'm running Maven 2.0.9 on Windows JDK 1.5 through Cygwin. We h
On Fri, 04 Jul 2008 10:01:43 Peter Horlock wrote:
> Hm, but for such analysis, isn't that what subversion is for?!
sure but where to look, if you built a snapshot what revision am i looking
for. If you have tags then you can easily see changes between checkpoints
--
Michael McCallum
Enterprise
On Fri, 04 Jul 2008 02:59:10 Peter Horlock wrote:
> 2008/7/3 Jörg Schaible <[EMAIL PROTECTED]>:
> > Sorry, but our priority is to ensure that all artifacts are built with
> > the same plugins and use the same artifact versions. In your model I have
> > to duplicate all the versions for your individ
On Fri, 04 Jul 2008 02:43:03 Jörg Schaible wrote:
> Sorry, but our priority is to ensure that all artifacts are built with the
> same plugins and use the same artifact versions. In your model I have to
> duplicate all the versions for your individual service parents. That's what
> I call an anti-pa
On Fri, 04 Jul 2008 03:59:29 Peter Horlock wrote:
> Sorry, but what's the purpose of the release plugin anyway? It's site
> doesn't really tell it:
> http://maven.apache.org/plugins/maven-release-plugin/
Very good question and simple to answer...
release-prepare - the release plugin will build an
On Fri, 04 Jul 2008 02:52:09 Peter Horlock wrote:
> The problem I see with version ranges, is you start loosing control.
Not true it means you have complete control. Unless you use [1.5] in all your
versions you are asking maven to make a best effort to give you 1.5.
> I guess the vital part to m
On Fri, 04 Jul 2008 10:08:44 Peter Horlock wrote:
> As I asked you before -
>
> when using version ranges, how can you ensure an upcoming 2.4 dependency
> will not break your build that was working with 2.3 ?!
there are a few ways but mostly its development process
0) communication
0) planning
Try with ${pom.version} this must be equivalent to ${project.version} but we
never know.
Jeff MAURY
On Fri, Jul 4, 2008 at 12:27 AM, Morgovsky, Alexander (US - Glen Mills) <
[EMAIL PROTECTED]> wrote:
> I posted here to get an answer to a maven question, so your response
> doesn't help me solve m
On Thu, Jul 3, 2008 at 4:34 PM, Chris Berry <[EMAIL PROTECTED]> wrote:
> I was going to try out the true for the
> maven-war-plugin, but I don't know where to get it from??
> Do I need to build it myself from the SVN trunk??
Building it yourself is an option, but if you're not already doing
that
Thanks Wendy.
I was going to try out the true for the
maven-war-plugin, but I don't know where to get it from??
Do I need to build it myself from the SVN trunk??
So to be clear, if I use , will this cause a JAR to be
automatically installed in my local repo (for mvn install) and
automatical
On Thu, Jul 3, 2008 at 4:07 PM, Chris Berry <[EMAIL PROTECTED]> wrote:
> Still what I find confusing is that the deploy plugin is aware of SNAPSHOTs
> versus Releases -- and it chooses the URL dynamically from
> distributionManagement -- so it seems that deploy-file could too??
I've never seen de
Hi Wendy,
With all due respect, having to build 3 separate projects, all within
a multi-project -- so 4 projects where there was once 1 -- certainly
doesn't seem to be in line w/ "keeping it simple". Especially when
all we want is some different packaging for the same raw classes/
resourc
On Thu, Jul 3, 2008 at 3:40 PM, Chris Berry <[EMAIL PROTECTED]> wrote:
> I am generating several artifacts from my build; a WAR, a TAR.GZ, and a JAR
> -- as required by downstream usage scenarios (embedded, standalone, or
> webapp)
> The project has WAR packaging. But I need to supply a JAR and T
Greetings,
I am generating several artifacts from my build; a WAR, a TAR.GZ, and
a JAR -- as required by downstream usage scenarios (embedded,
standalone, or webapp)
The project has WAR packaging. But I need to supply a JAR and TAR.GZ
as well. The TAR.GZ is easy -- using the assembly plugin
I posted here to get an answer to a maven question, so your response
doesn't help me solve my issue. But since you went down on this road,
the message says:
This message (including any attachments) contains confidential
information
> intended for a specific individual and purpose, and is protect
Hi, also tried using the command prompt and typed
mvn install:install-file -DgroupId=javax.media -DartifactId=jai_core
-Dversion=1.1.3 -Dpackaging=jar -Dfile=/path/to/file but wanted to ask, the
Dfile=/path/to/file, is this the actual jar file? because i still get a
BUILD FAILURE. Please help guys
As I asked you before -
when using version ranges, how can you ensure an upcoming 2.4 dependency
will not break your build that was working with 2.3 ?!
Thanks,
Peter
If instead you want to do the opposite, unpacking a dependency but avoid to
copy the artifact under lib, you can just add a dependencySet with an
for the artifact you do not want.
For example, let's say in the pom you have:
connector-testing-framework
funambol
Hm, but for such analysis, isn't that what subversion is for?!
On Fri, 04 Jul 2008 02:29:07 Jörg Schaible wrote:
> >
> > I can release any artifact any time... i live on the ready to release
> > to production rather than beginning of build cycle line. Subtle but
> > fundamental difference. And the overhead is minimal.
>
> The overhead is that you produce a lot
Hi am reading the ImageLabe lesson
http://docs.codehaus.org/display/GEOTDOC/08+ImageLab
http://docs.codehaus.org/display/GEOTDOC/08+ImageLab and have added the JAR
dependecy code for both Java Advanced Imaging and Image IO. However, after
did that and did a clean and build process i got a few er
Kathryn Huxtable wrote:
I don't see that MSITE-274 (spaces added) is fixed. I'm still getting
the extra spaces. -K
I don't get the extra spaces when I specify version 2.0-beta-7. Did you
explicitly say this in your POM?
...
org.apache.maven.plugins
maven-sit
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > 8) use mvn dependency:resolve and mvn
> > depedendency:tree regularly to understand how things are working and
> > to catch any
> > transitions that i did not
> > expect
>
> Especially after upgrading version of 3rd party artifacts ;-)
Actually
That makes pretty good sense.
I won't be having enough time today to finish implementing your solution,
though I am almost all done.
So, from what I understand, you do keep your jar dependencies in a lib
folder or some other sort of external storage, correct?
Would it be possible for me to, afte
On Thu, Jul 3, 2008 at 5:12 PM, André Kelpe
<[EMAIL PROTECTED]> wrote:
> Hi Jan!
>
>> I'm running Maven 2.0.9 on Windows JDK 1.5 through Cygwin. We have set
>> up Proximity as a corporate proxy and I have followed the guide in the
>> Sonatype book to configure repositories and mirrors in my setting
If anyone's still interested, I've actually resorted to disabling the central
repository completely. Here's what I added to my pom so that no checks are
done at all -
central
http://repo1.maven.org/maven2
false
false
manish wrote:
>
Hi all,
My projects are organized in a standard way with a top level pom that
lists out the general dependencies and versions to be used for all the
child projects that would inherit from it. However, i am facing a
situation where i need a different version of a particular dependency in
a particul
I don't see that MSITE-274 (spaces added) is fixed. I'm still getting
the extra spaces. -K
On Jul 3, 2008, at 12:34 AM, Dennis Lundberg wrote:
The Maven team is pleased to announce the release of the Maven Site
Plugin, version 2.0-beta-7
The Maven 2 Site plugin is used to generate a site for
Click on the release plugin goals from the page you linked to and the docs
describe exactly what it does... for example see:
http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html.
You'll start appreciating the release plugin when you have a multimodule
project with tens
Hi James,
Not possible to use mavens war plugin, as an external tool (Portlet
Factory) is creating the war file.
I need the packaging type to remain as war. This is to ensure maven
correctly performs the install operation into the repository, as well as
the use of release plugin.
So I really need
P.s.: It's really sad that there is no book / website that answers all these
kind of "best practice" answers.
The upcoming mvn book "the definitive guide" is great, yet imho it's more
focused on basics. :-(
Peter
>
>
> Last point: The release plugin will fail to update the version of your
> current project if it is defined by a property.
>
Sorry, but what's the purpose of the release plugin anyway? It's site
doesn't really tell it:
http://maven.apache.org/plugins/maven-release-plugin/
If I got it right,
Peter Horlock wrote:
>> Neither Michael nor I did propose properties for the version. Simply
>> define the version in the version depMgmnt itself and you're done.
>
>
> No, I don't think so, my point is:
>
> parent pom:
>
>
> [...]
> 1.2.3
> [...]
>
>
> submodule:
> [...]
> 1.2.3
> [...]
>
Hi Peter,
Peter Horlock wrote:
> 2008/7/3 Jörg Schaible <[EMAIL PROTECTED]>:
>
>> Sorry, but our priority is to ensure that all artifacts are built
>> with the same plugins and use the same artifact versions. In your
>> model I have to duplicate all the versions for your individual
>> service par
Hi Jan!
> I'm running Maven 2.0.9 on Windows JDK 1.5 through Cygwin. We have set
> up Proximity as a corporate proxy and I have followed the guide in the
> Sonatype book to configure repositories and mirrors in my settings.
>
> Adding this block to my POM:
>
>
>
>
> org.apache.maven.pl
> Neither Michael nor I did propose properties for the version. Simply define
> the version in the version depMgmnt itself and you're done.
No, I don't think so, my point is:
parent pom:
[...]
1.2.3
[...]
submodule:
[...]
1.2.3
[...]
So you will have to change it in two places (=duplicate c
Hi Peter,
Peter Horlock wrote:
> The problem I see with version ranges, is you start loosing control.
> I guess the vital part to make the use of version ranges work (at
> all) is that every developer has to follow the rule
>
> major.minor.patch...
>
> So far, we have been very loose with versio
2008/7/3 Jörg Schaible <[EMAIL PROTECTED]>:
> Sorry, but our priority is to ensure that all artifacts are built with the
> same plugins and use the same artifact versions. In your model I have to
> duplicate all the versions for your individual service parents. That's what
> I call an anti-pattern
The problem I see with version ranges, is you start loosing control.
I guess the vital part to make the use of version ranges work (at all) is
that every developer has to follow the rule
major.minor.patch...
So far, we have been very loose with versions - Someone changes 5 lines in
the code, make
Michael McCallum wrote:
> On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
>>> 6) start version numbering 1.1 for new artifacts
>>> * makes ranges work better
>>> * who needs the extra .0 on the end, i save that for patches
>>
>> Why's that? Also remember that version 1 is implicitly 1.0.0.0
>
Michael McCallum wrote:
> On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
>>> 12) set up parents that define plugins for particular types of
>>> projects i.e. webapps, jars, parents,
>>
>> We setup the common settings in the pluginMgmnt of the global POM
>> ... and lock down the plugin versions.
Michael McCallum wrote:
> On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
>>> hibernate.composite 7.x uses hibernate 3.2.6ga, uses ehcache
>>> 3.0, uses
>>> cglib... excludes commons-logging, excludes ehcache, excludes
>>> cglib-full and all my projects the use hibernate use
>>> hibernate.composi
Greetings,
I'm attempting to follow best practice and lock down plugins in our
parent POM. From what I understand, I should use a version range
instead of a plain version number to accomplish a true lock down for
future reproducibility. E.g. for the clean plugin I would use [2.2]
instead of just 2
Michael McCallum wrote:
> On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
>>> project.deployable uses implementation.[1,2-!) and consumer.[1,2-!)
>>> obviously in the real world things aren't this simple and for
>>> simple cases this seems like excessive overhead
>>
>> We do not use ranges at al
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > 8) use mvn dependency:resolve and mvn
> > depedendency:tree regularly to understand how things are working and
> > to catch any
> > transitions that i did not
> > expect
>
> Especially after upgrading version of 3rd party artifacts ;-)
Actually
Hi,
I'm trying to write my own Mojo, but I'm facing an issue.
I create it using :
mvn archetype:create -DgroupId=com.sonatype.maven.plugins
-DartifactId=first-maven-plugin
-DarchetypeGroupId=org.apache.maven.archetypes
-DarchetypeArtifactId=maven-archetype-mojo
When I try to install it (mvn inst
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > project.deployable uses implementation.[1,2-!) and consumer.[1,2-!)
> > obviously in the real world things aren't this simple and for
> > simple cases
> > this seems like excessive overhead
>
> We do not use ranges at all. Works great without.
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > 6) start version numbering 1.1 for new artifacts
> > * makes ranges work better
> > * who needs the extra .0 on the end, i save that for patches
>
> Why's that? Also remember that version 1 is implicitly 1.0.0.0
so that range [1,2-!) does incl
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > 12) set up parents that define plugins for particular types
> > of projects i.e.
> > webapps, jars, parents,
>
> We setup the common settings in the pluginMgmnt of the global POM ... and
> lock down the plugin versions.
not quite what i was get
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > hibernate.composite 7.x uses hibernate 3.2.6ga, uses ehcache
> > 3.0, uses
> > cglib... excludes commons-logging, excludes ehcache, excludes
> > cglib-full and all my projects the use hibernate use
> > hibernate.composite.[7,8-!)
>
> We make the
> > The things i do
> > 1) parent version are always release versions
>
> 2) all depedencies are always release versions
>
> Why no snapshots?! In our company, often many people are working on the
> same projects, e.g. that contains shared, "common" classes -
> So it can happen that there will be
Sebastien,
I'm not sure you can do that. You *could* try to change the packaging
of your project from "war" to "jar" and see if that helps (But good
luck with that).
Id highly suggest that you use the maven war plugin.
Cheers
James
On 03/07/2008, at 1:27 PM, Sebastien Hadjifotis wrote:
Hi all,
I'm trying to add a classPath entry to the manifest of a jar built with
maven. the entry I'm trying to add is a folder that will be on the same
directory of the jar in the final installation.
I've search the documentation but didn't find anything useful. Can someone
give me a hint?
than
Greetings,
I am generating several artifacts from my build; a WAR, a TAR.GZ, and
a JAR -- as required by downstream usage scenarios (embedded,
standalone, or webapp)
I am having trouble deploying the JAR properly. (Note: I had to add an
install:install-file section to my POM to get the JA
Hello,
I am using maven ant task that runs a tool to generate a war file.
This works fine. My issue is howdo Itell maven to not try to build the war
file iteself using the war plugin?
Cheers,
Sebastien Hadjifotis
-
To unsubscr
What is wrong with having a static method that returns the string from
a parallel properties file...
something like
public class MyFoo {
private static String getProp(String name) {
Properties props = new Properties();
final String resourceName = MyFoo.class.getSimpleName() +
Hi list,
I copied this from
http://maven.apache.org/plugins/maven-surefire-plugin/examples/inclusion-exclusion.html
and put it in a profile:
RESOURCE_LOCAL
RESOURCE_LOCAL
org.apache.maven.plugins
maven-surefire-
Hi,
I am facing a problem. I have a java class which contains final String.
This string has to be final, so I can not set value by a file
properties.
This string is different according to each environment, so I would like
to change it during the maven build by using maven profile.
But I do
Hi list!
I'm using the webstart-maven-plugin, building a war file using the
jnlp-download-servlet goal, and everything works fine until now. But I'm
doing some RMI stuff, and I need the java.rmi.server.codebase property
correctly set. Doing some debug, I found that the codebase is being set
t
Hi,
I have been facing the same problem. It's a maven-assembly-plugin2.2-beta-2
bug; check http://jira.codehaus.org/browse/MASSEMBLY-328 .
The workaround I found is to specify the version 2.1 of the
maven-assembly-plugin in my pom, normally your artifact will correctly be
installed in your reposit
Hi,
Is someone working on MNG-2802 ?
Is there a workaround for this? this is very important for CI.
Benoit
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
I want to let Maven / the Resource plugin (
http://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html
)
parse my source code to replace {project.version} with the current version
of the project as defined in the pom.
This works great, but - in JSTL, as well as in Op
On Thu, Jul 3, 2008 at 3:43 AM, Rakesh Sinha <[EMAIL PROTECTED]> wrote:
> To develop a plugin of ours - we need to port it to Eclipse 3.4.0
> and we have the maven build script for the same.
>
> Can we have the jars available for 3.4.0 here at the maven repository.
>
> http://repo1.maven.org/m
Yes, it worked manually from my console.
Also, now I finally got an idea of how to not duplicate the scm connection
details for every project,
i just added:
scm:svn:${svn-repository}/${project.artifactId}
scm:svn:${svn-repository}/${project.artifactId}
${svn-repository}/${project.art
I have a multimodule project (Apache JAMES Server) having dependencies
on javax.mail:mail:1.4.1 artifact. I manage the dependency in the
dependencyManagement of the parent pom and then I declare the dependency
in each module depending on that artifact.
Now I know that geronimo publish its own
Hello,
I try to upgrade maven from 2.0.8 to 2.0.9. I have pb with a system
dependency:
Here are the dependencies in a parent pom:
com.sun
tools
1.4.2
system
${java.home}/../lib/tools.jar
When
Mikel Cármenes Cavia wrote:
Well, that sure sounds like another very intelligent way to do it. Would you
mind sharing the portion of your POM that takes care of this sort of
functionality?
Ok, here we go ...
Step 1: list all the dependencies into a text file
org.apache.maven.plugins
m
FYI, You are not allowed to use ${blah} in the project/parent/version
or project/version tags.
There are bugs in Maven that mean it won't blow up in obvious ways if
you do use ${blah} in those two tags... but it will blow up when you
least expect it
You can use ${blah} in
project/dependencies/d
Even the 3.3.3 is not located there ;(
2008/7/3 Rakesh Sinha <[EMAIL PROTECTED]>:
> Hi -
> To develop a plugin of ours - we need to port it to Eclipse 3.4.0
> and we have the maven build script for the same.
>
> Can we have the jars available for 3.4.0 here at the maven repository.
>
> http://
Hi Michael,
well it seems everybody has some different scheme that works for him/his
company.
Michael McCallum wrote:
> On Thu, 03 Jul 2008 00:44:20 Peter Horlock wrote:
>> Could you be a bit more precise? (Just make it plain simple, this
>> increases the chance that I get it! ;-)
> I suppose
>
79 matches
Mail list logo
