I hope I get this right
Jason here states that there should only be one central
And yes we can ONLY have ONE central. And this is the ONE we got
today
That must be the game we are playing.
The community must be able to TRUST maven / central.
Starting changing this could cause doubt, and
if you're using the m2eclipse plugin, building project b will force a
build of project a... but all the jar files will be installed into and
resolved from your local maven repository (~/.m2/repository), not the
target directory.
Not sure why you would want the jar files in your target
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will force
a build of project a... but all the jar files will be installed into
and resolved from your local maven repository (~/.m2/repository),
not the target directory.
The
On Sep 27, 2009, at 11:26 AM, Jason van Zyl wrote:
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will force
a build of project a... but all the jar files will be installed
into and resolved from your local maven repository
On 2009-09-27, at 8:30 AM, Nayan Hajratwala wrote:
On Sep 27, 2009, at 11:26 AM, Jason van Zyl wrote:
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will
force a build of project a... but all the jar files will be
installed
I agree that a point system is pointless.
I mostly care about whether an artifact is well-formed. I don't depend on
maven central to help me make business decisions about what open source
components to depend on. If I need a component, I do the research to see
what exists, what has a live
This is exactly what all sane users do, but we will still try
extremely hard to clean everything up and make it easier for open
source projects to get their artifacts to central.
On 2009-09-27, at 10:41 AM, Benson Margulies wrote:
I agree that a point system is pointless.
I mostly care
Mr. Zyl,
Please don't mistake me. I'm on your side of this debate. I am no more
arguing against basic cleanup than I am arguing for trying to get into the
business of arbitrating and publishing elaborate metadata about what is
inside or behind the artifacts.
Central should be as clean as
Only pointing out that's what people typically do.
On 2009-09-27, at 11:27 AM, Benson Margulies wrote:
Mr. Zyl,
Please don't mistake me. I'm on your side of this debate. I am no more
arguing against basic cleanup than I am arguing for trying to get
into the
business of arbitrating and
I believe that openArchitectureWare also uses the eclipse-formatter. At
least they have several eclipse-jars in their repo (although I honestly
have no idea how old/new thea are). You might want to check those out?
http://www.openarchitectureware.org/m2/
Roland
there are some jars already
It's looking for dependencies in target/classes? Really?
Normally, Maven reads the POM in the directory you start it from. If this
POM contains modules, those are loaded as well (and if they have modules,
those are loaded too... ad infinitum). Then, if some of those modules have
dependencies to
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will force
a build of project a... but all the jar files will be installed into
and resolved from your local maven repository (~/.m2/repository),
not the target directory.
The JARs
On 2009-09-27, at 1:40 PM, Roland Asmann wrote:
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will force
a build of project a... but all the jar files will be installed into
and resolved from your local maven repository
On 2009-09-27, at 1:40 PM, Roland Asmann wrote:
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will force
a build of project a... but all the jar files will be installed into
and resolved from your local maven repository
On 2009-09-27, at 2:08 PM, Roland Asmann wrote:
On 2009-09-27, at 1:40 PM, Roland Asmann wrote:
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will
force
a build of project a... but all the jar files will be installed
into
On Mon, Sep 28, 2009 at 7:07 AM, Jason van Zyl jvan...@sonatype.com wrote:
I just ran it on a project and that's not what it did. I'm not talking only
about multi-module projects but other projects you may refer to. I'm often
working on several related projects where I need to work with them
On 25/09/2009, at 6:24 PM, Entner Harald wrote:
The ant script has in my opinion a bad side effect. The structure is
not allowed to change, so i would prefer to use dependencies so
structure changes would have no side effects.
Currently i use the maven-dependency-plugin that copies the
It seems you have pegged the webdav provider to 1.0-beta-2.
I'd suggest removing that build extension, or replacing it with:
g: org.apache.maven.wagon
a: wagon-webdav-jackrabbit
v: 1.0-beta-6
Cheers,
Brett
On 25/09/2009, at 7:48 PM, Marc Lustig wrote:
I tried using Mvn 2.2.1 and got the
It looks like when they were added, they were not properly hidden
from plugin classes. So you will need to ensure you use the exact
version of the library that is used in Maven.
Please report this at http://jira.codehaus.org/browse/MNG so it can be
corrected in future.
Thanks,
Brett
On
On Mon, Sep 28, 2009 at 7:07 AM, Jason van Zyl jvan...@sonatype.com
wrote:
I just ran it on a project and that's not what it did. I'm not talking
only about multi-module projects but other projects you may refer to.
I'm often working on several related projects where I need to work with
On 27/09/2009, at 5:15 AM, Jason van Zyl wrote:
Not having a super high quality central repository actually makes
our commercial efforts a lot harder. If I was devious I would have
agreed with Brett and would make a completely clean central
repository as our plans require intact
On Sun September 27 2009 7:28:48 pm Brett Porter wrote:
On 25/09/2009, at 6:24 PM, Entner Harald wrote:
The ant script has in my opinion a bad side effect. The structure is
not allowed to change, so i would prefer to use dependencies so
structure changes would have no side effects.
Brian, it just sounds awfully complex. A simple matter such as sharing a
log4j.property at the root of a nested project shouldn't create so much
work. Any other avenue? I am glad you shared this information.
Paul
On Sat, Sep 26, 2009 at 10:12 PM, Brian Fox bri...@infinity.nu wrote:
Something
That's right maven is looking for a dependency in taget/classes, see below
for the log. The one I'm referring to is
C:\SVNHome\CDF-trunk\cdf-webtas\cdf-webtas-overrides\target\classes,
it should be referencing the jar, right?
How can this happen? So far I have only seen this on the one system I
Why don't you just create a submodule only containing that logging
configuration (and possible other shared classpath resources) and make
it a dependency of all the other modules? That's what we do.
Kalle
On Sun, Sep 27, 2009 at 6:27 PM, Paul Benedict pbened...@apache.org wrote:
Brian, it just
Hello,
I just updated my eclipse configuration today, and it is complaining now
about things that aren't absolutely understandable to me. The plugins
mentioned in the output below aren't defined by my project and should be use
whatever is default. The project has an extra m2 builder defined to
Just found it. the setting for the Maven runtime in the builder
configuration dialog was hidden because the configuration window was a
little too small. Looks like an eclipse issue.
It is not necessary to create a new repo and it is not necessary to
modify anything on Central or the policies how it is managed. Mess
could be cleaned up virtually if I could attach a filter.
In the ~/.m2/settings.xml for example, I should be able to add a list
of repository addresses and for
28 matches
Mail list logo
