1.0
> >>>../parent/pom.xml
> >>>
> >>
> >> WTF? How is this possible? Who signed this? The API should be completely
> >> decoupled of Weld. The repo is burried in the parents. This is
> >> absolutely unacceptable. It l
If you configure a constant value in your POM then that takes precedence
over values from the command-line.
If you want to make the value configurable on the command-line and have a
default value in your POM then the recommended approach is to introduce a
property:
some-default-value
notation.Priority(Integer.MAX_VALUE)
to RedissonSyncContextFactory - this will give that component the highest
priority, so it will always appear before any other implementation of that
interface.
On Wed, 12 Aug 2020 at 10:17, Stuart McCulloch wrote:
> The issue is indeed with AetherMo
w how this could be done.
On Tue, 11 Aug 2020 at 12:07, Michael Osipov wrote:
> Am 2020-08-11 um 11:48 schrieb Stuart McCulloch:
> > JSR330 annotation scanning is enabled for all realms including
> > extensions, so it should be picked up.
> >
> > Does the replacement im
JSR330 annotation scanning is enabled for all realms including
extensions, so it should be picked up.
Does the replacement implementation have the same "hint" or name?
ie. @Named("default")
You can turn on detailed container logging with -Dsisu.debug which will log
all bindings discovered in each
It looks like you're missing the tag inside the
list:
https://maven.apache.org/plugins/maven-shade-plugin/examples/class-relocation.html
try:
javax.ejb
jakarta.ejb
javax.ejb.*
On Mon, 4 May 2020 at
hare/maven
> Java version: 11.0.5, vendor: Private Build, runtime:
> /usr/lib/jvm/java-11-openjdk-amd64
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.0.0-37-generic", arch: "amd64", family:
>
The Java 11 warning mentions that "/usr/share/maven/lib/guice.jar" has a
class named "com.google.inject.internal.cglib.core.$ReflectUtils$1"
This looks suspect because the official Maven distribution uses the
"no-AOP" version of Guice which doesn't contain any CGLIB classes. It
suggests that whoev
How are you replacing them currently?
The typical way is to use the extensions mechanism:
https://maven.apache.org/docs/3.3.1/release-notes.html#Core_Extensions
Components contributed via an extension have a higher priority over the
original component in core (assuming that they have the same JSR
ModelResolver isn't a component and therefore isn't available for injection
- I can see two implementations of that interface in Maven, but both are
manually created:
https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java#L276
ht
I believe that's true for the current releases, but it looks like it will
change in the future:
https://github.com/AdoptOpenJDK/openjdk-build/issues/465
On Sun, 4 Nov 2018 at 19:46, Elliot Huntington
wrote:
> Now that Oracle is charging licensing fees to use Oracle Java as of Java
> 11, I am swi
On 3 Feb 2017 16:44, "Laird Nelson" wrote:
On Fri, Feb 3, 2017 at 1:15 AM Hervé BOUTEMY wrote:
> notice:@Component we're using in a Mojo is from Maven Plugin Tools
> org.apache.maven.plugins.annotations.Component [1]
>
Right; I (now :-)) understand this part and all of the things related to it
Here's a brief overview of the different layers...
Maven plugin annotations are only used at plugin build time to generate
Maven's plugin.xml - they are not used at runtime (at least the container
doesn't use them)
Maven uses this plugin.xml descriptor to setup the plugin in Plexus
(creating the
o my change should be good for commit for 3.4?
> >
> > -Dan
> >
> > On Sun, Nov 13, 2016 at 3:01 PM, Stuart McCulloch > (mailto:mccu...@gmail.com)>
> > wrote:
> >
> > > Hi Dan,
> > >
> > > There are two places in Mave
able to get
> @PostContruct working yet
>
> Thanks
>
> -Dan
>
> On Sun, Sep 11, 2016 at 7:27 PM, Dan Tran (mailto:dant...@gmail.com)> wrote:
>
> > Thanks Stuart, very much appreciated
> >
> > -D
> >
> > On Sun, Sep 11, 2016 at 7:22 PM, Stuart
You could write a custom enforcer rule to check the classifier of projects
with particular groupIds:
http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html
Then configure the enforcer plugin to apply that rule in your corporate pom
or wherever you want to enforce it...
On 22 Oc
om)> wrote:
> >
> > > here you go https://issues.apache.org/jira/browse/MNG-6084
> > >
> > > Very much appreciated
> > >
> > > -Dan
> > >
> > > On Fri, Sep 2, 2016 at 8:42 AM, Stuart McCulloch > > (mailto:mccu...@gmai
)
>
> should I file a JIRA to enable JSR-250 support fo rmaven 3.4?
Sure - send me the ticket number and I’ll add some commentary this weekend
> looking forward to use it
>
> Thanks
>
> -Dan
>
>
>
> On Wed, Aug 31, 2016 at 9:22 AM, Stuart McCull
Hi Dan,
Constructor injection (and component injection) is working for me with Maven
3.3.9 if I follow the example in http://maven.apache.org/maven-jsr330.html
Is your plugin code available somewhere?
PS. at the moment Maven doesn’t enable container support for JSR-250 lifecycle,
but it is
If you don’t configure a specific version in your pom for one of the standard
plugins, Maven will use the version specified in the default lifecycle bindings.
For example Maven 3.3.3, defaults to maven-compiler-plugin 3.1:
https://github.com/apache/maven/blob/maven-3.3.3/maven-core/src/main/reso
On Monday, 25 May 2015 at 09:46, WonderCsabo wrote:
> The documentation says it includes these resources by default, but apparently
> it never does.
>
> After examining the code, it seems CheckstyleViolationCheckMojo.execute()
> forgets to call request.setTestResources(), hence that is always null
20 873
> CH: +41 79 107 92 27
> christian.eugs...@gmx.net
>
>
>
>
> > Am 27.03.2015 um 17:50 schrieb Stuart McCulloch :
> >
> > I see you're declaring dependencies with bundle whereas you
> > should just leave them with the default type (jar). While the pa
I see you're declaring dependencies with bundle whereas you
should just leave them with the default type (jar). While the packaging
type is "bundle" (to activate the different packaging lifecycle) the
artifacts produced are declared as type jar and can be referenced as
dependencies with the default
The log shows that it’s looking for artifacts with an extension of ‘bundle’,
whereas the bundle packaging type actually produces artifacts with an extension
of ‘jar’ - this suggests that the bundle lifecycle extension has not been
installed for the itest project.
What does the sip-detection pom
On Thursday, 19 March 2015 at 10:41, Markus Karg wrote:
> As I said I cannot reproduce the bug anymore, so do you think the requested
> test makes any sense still?
>
>
The Nexus system feeds record authz/authc events as well as any upload attempts:
http://books.sonatype.com/nexus-book/refere
class as suggested
> here: https://wiki.eclipse.org/Sisu/PlexusMigration
>
> @Named
> > public class MyPluginModule extends com.google.inject.AbstractModule {
>
> public void configure() {
> > bind(MyInterface.class).annotatedWith(Names.named("default")).to(
>
Assuming you’re using Maven 3.1.1 or later then yes, that should work.
--
Cheers, Stuart
On Monday, 16 March 2015 at 18:09, Cristiano Gavião wrote:
> Hello,
>
> I've create a mojo and set it to use sisu based injection.
>
> I added to this mojo a constructor like this:
>
> @Inject
> p
Use the jar-no-fork and test-jar-no-fork goals of the maven-source-plugin -
these won’t fork the build (which is what is causing initialize to run multiple
times)
On Thursday, 15 January 2015 at 16:24, org.apache.maven.u...@io7m.com wrote:
> Hi.
>
> I have a custom plugin that inserts some ex
On Monday, 8 December 2014 at 16:24, Paul Benedict wrote:
> I configured the WAR plugin to overlay a zip file. Nothing fancy. Here's
> the config:
>
>
> org.apache.maven.plugins
> maven-war-plugin
> 2.5
>
>
> org.company
>
>
^ missing ... ?
> ui
> zip
>
>
>
>
> I get an exception:
> j
Does your pom have a release profile that executes gpg signing? ie. like in
https://github.com/sonatype/oss-parents/blob/master/forge-parent/pom.xml
On 9 Nov 2014 11:51, "Simon Taddiken" wrote:
> Hi,
>
> I'm trying to introduce a common parent pom for my projects. So I have
> created a maven arti
On Wednesday, 22 October 2014 at 14:08, Michal Konopa wrote:
> Hello all,
> I'm experimenting a little bit with aggregating Javadoc from dependency
> sources - according to:
> http://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate-dependency-sources.html
>
> document.
>
> I put
On 19 Sep 2014 11:12, "Stuart McCulloch" wrote:
>
> On 19 Sep 2014 09:09, "Edmond chouaffé" wrote:
> >
> > Hi guys.
> >
> > I have been struggling to get systemPropertyVariables from the
maven-surefire-plugin working.
> > I am runni
On 19 Sep 2014 09:09, "Edmond chouaffé" wrote:
>
> Hi guys.
>
> I have been struggling to get systemPropertyVariables from the
maven-surefire-plugin working.
> I am running an ubunto machine where I have defined the JBOSS_HOME
variable as such in the .profile file: export JBOSS_HOME=test.
> Howeve
I wonder if this might be related to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=418250 ?
On 27 Aug 2014, at 04:35, Juven Xu wrote:
> maven: 3.1.1
> jdk: 1.7.0_25 Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)
>
> the error message is:
>
> [INFO] Building buy-client 1.1.8-o2o630
Each Maven distribution has various built-in defaults, you can see the defaults
for 3.2.1 here:
https://github.com/apache/maven/blob/maven-3.2.1/maven-core/src/main/resources/META-INF/plexus/default-bindings.xml
The compiler plugin is explicitly set to 2.5.1 unless you override the version
On 16 May 2014, at 22:59, Dan Tran wrote:
> umm, what worries me why it disappears from maven central which suppose to
> be a well guarded place?
It has not disappeared as it was never on central in the first place - it's
just a placeholder GAV that m2e uses for configuration purposes. You shou
I don’t believe it ever existed on central, IIRC it’s a placeholder used by
m2e: http://stackoverflow.com/a/7423909
On 16 May 2014, at 20:48, Dan Tran wrote:
> any one?
>
> http://central.maven.org/maven2/org/eclipse/m2e
>
> Thanks
>
> -D
>
>
> On Thu, May 15, 2014 at 4:34 PM, Dan Tran wr
Also check your java imports, just in case you’ve imported a different Logger
by mistake (such as java.util.logging.Logger)
On 30 Apr 2014, at 12:48, Nick Stolwijk wrote:
> You can use the dependency:tree[1] goal to view a tree of your
> dependencies to see if the correct version of Log4J is b
that maven-dev
discussion.
> Martin Grigorov
> Wicket Training and Consulting
>
> On Thu, Apr 17, 2014 at 5:12 PM, Stuart McCulloch wrote:
>
>> See
>> http://mail-archives.apache.org/mod_mbox/maven-dev/201402.mbox/%3ca70f13ef-38e2-49a8-b696-b5e592092...@gmail.com%3ef
See
http://mail-archives.apache.org/mod_mbox/maven-dev/201402.mbox/%3ca70f13ef-38e2-49a8-b696-b5e592092...@gmail.com%3e
for why this is happening
AFAICT neither of the suggested solutions mentioned in the above email have
been applied to DefaultClassRealmManager, so I believe this is still an i
on between core and a plugin.
> What would be need to make it not filter out a maven-core library that is a
> different version of the running Maven instance?
You can’t without doing some complicated class loader hacks, this is a
fundamental feature of Maven’s plugin system.
> William
>
On 28 Feb 2014, at 01:17, William Ferguson
wrote:
> As part of the development of the android-maven-plugin we have need to add
> in an AbstractMavenLifecycleParticipant so that we can modify the compile
> classpath to add artefacts that are contained within a project's
> dependencies. Igor provi
On 15 February 2014 11:13, 454329 wrote:
> Hi there ,
>
> I have this dependency present in my pom.xml .
>
> org.apache.solr
> solr-cell
> 4.0
>
Did a quick search for solr-cell on http://search.maven.org/ and I suspect
the
us instance (enabled to download remote indexes)
But I just tried from a fresh installation with the default repo to confirm
and it is in the latest index with nexus.index.timestamp=20140216125157.106
> All the best,
> DaveLaw
>
> On 16.02.2014 14:36, Stuart McCulloch wrote:
>
&
On 16 February 2014 10:31, David Law wrote:
> Hi Mirko,
>
> I think though 6 days!!! should be adequate for that.
> In fact, I think 6 minutes should be adequate.
>
> So I really need someone to explain how I can move forward with this issue.
>
FWIW, I did a search today for org.apache.poi:poi i
On 15 February 2014 15:51, Thomas Broyer wrote:
> On Sat, Feb 15, 2014 at 4:18 PM, Baptiste Mathus
> wrote:
>
> > Hi Dan,
> > Not sure what you mean. You say "CI", are you taking about a specific
> > server? If Jenkins for example, wouldn't it then be more a Jenkins user
> ml
> > question?
> >
>
On 13 Feb 2014, at 17:46, Dan Tran wrote:
> A contributor for MOJO-2006 [1] uses array configuration at
>
> http://maven.apache.org/guides/plugin/guide-java-plugin-development.html (
> array session)
>
> here is the text
>
>/**
> * My List.
> */
>@Parameter
>private List my
On 5 Feb 2014, at 13:23, Melvyn de Kort wrote:
> Our maximum heap size is already 4G, can't increase that any more I'm
> afraid.
It could be running out of PermGen space, which is controlled by a different
setting:
MAVEN_OPTS="-XX:MaxPermSize=256m"
> Regards,
>
> Melvyn de Kort
>
>
On 3 Feb 2014, at 14:44, Stuart McCulloch wrote:
> On 3 Feb 2014, at 14:34, Benson Margulies wrote:
>
>> Does anyone recognize the following? It correlates with a mystery.
>
> Looks like http://jira.codehaus.org/browse/MASSEMBLY-671 … basically it
> happens when there
On 3 Feb 2014, at 14:34, Benson Margulies wrote:
> Does anyone recognize the following? It correlates with a mystery.
Looks like http://jira.codehaus.org/browse/MASSEMBLY-671 … basically it happens
when there’s a problem with the assembly descriptor which then triggers a code
path that leads t
On 15 Jan 2014, at 08:20, Mikael Petterson
wrote:
> Hi,
>
> New try :-)
>
> I have the following:
>
> Interface in dependency jar javadoc:
>
> /**
> * Deletes the object found at the specified location.
> *
> * @param Object any type of object
> * @throws InvalidObjectExcep
On 5 Jan 2014, at 13:15, Tommy Svensson wrote:
> I was asked to submit one of my opensource tools at github to maven central.
> This turned out to be a rather complex procedure.
[ disclaimer: I work at Sonatype ]
Any suggestions for improving the process are welcome - most of the
requirements
On 19 Dec 2013, at 15:31, Jeremy Whiting wrote:
> Hi,
> I am using the maven-plugin-plugin for a hibernate project to provide a user
> plugin. I am finding the Mojo definition is not generated. I found a
> workaround for the issue. This discussion is related to the issue discussed
> here
> ht
dehaus.org/browse/WAGON-407
> -D
>
>
> On Mon, Dec 16, 2013 at 9:38 AM, Stuart McCulloch wrote:
>
>> Looks like a shading issue in maven-wagon/wagon-providers/wagon-http:
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p
Looks like a shading issue in maven-wagon/wagon-providers/wagon-http:
https://git-wip-us.apache.org/repos/asf?p=maven-wagon.git;a=blob;f=wagon-providers/wagon-http/pom.xml;h=1fd61e34da435024062a566f6bd68410d98fdc67;hb=HEAD#l87
It doesn’t shade in commons-io, commons-lang, or jsoup; despi
You could try replacing:
maven-3.1.1/boot/plexus-classworlds-2.5.1.jar
with:
maven-3.0.5/boot/plexus-classworlds-2.4.jar
in case the change to use unsynchronised class loading in classworlds 2.5 when
running on Java 1.7 is causing the issue.
On 5 Dec 2013, at 16:32, Collins So
a 1.7 to use the eclipse compiler in Maven,
just use the plugin configuration shown below and Maven will compile your code
using the eclipse compiler (also known as ecj).
> -Message d'origine-
> De : Stuart McCulloch [mailto:mccu...@gmail.com]
> Envoyé : lundi 2 décembre 201
On 2 Dec 2013, at 11:15, Adrien Ruffié wrote:
> I have found more information here:
>
> http://stackoverflow.com/questions/19266797/different-compilation-behavior-w
> ith-type-cast-between-eclipse-and-maven/19267547#19267547
>
> that say:
>
> "Eclipse comes with its own Java compiler; Maven us
Looks like http://jira.codehaus.org/browse/PLXCOMP-208 which was fixed in
plexus-archiver-2.2.
Which plugin was executing before the error? It should hopefully just be a
matter of updating your pom.xml to use a more recent version of the plugin
which depends on plexus-archiver-2.2 or later.
On
Update the lib-jenkins-maven-embedder dependency to version 3.11, since this is
the version that works with the latest aether/sisu dependencies.
On 20 Nov 2013, at 09:41, Bernd Adamowicz wrote:
> No answer so far. Should I file a bug? Any opinion?
>
> Bernd Adamowicz
>
>
> -Original Messa
BTW, I ran your pom.xml through:
mvn dependency:tree
using Maven3 and the exclusions for those 2 maven-plugins were respected, which
suggests your exclusion issue might also be specific to Gradle.
On 14 Nov 2013, at 14:53, Stuart McCulloch wrote:
> You mean the "POM relocati
plugins
> maven-cobertura-plugin
> plugin
>
>
>
> On Thu, Nov 14, 2013 at 9:32 AM, Jason Tesser wrote:
>
>> you are referring to the maven-plugins I think
>>
>> But what about the xml-api thing?
>>
>>
>> On Thu, Nov 14, 2013 at 9:29 AM, St
to the maven-plugins I think
>
> But what about the xml-api thing?
>
> On Thu, Nov 14, 2013 at 9:29 AM, Stuart McCulloch wrote:
>
>> Try adding:
>>
>>plugin
>>
>> to those 2 dependency exclusions.
>>
>> ( the jaxen pom:
>> ht
Try adding:
plugin
to those 2 dependency exclusions.
( the jaxen pom:
http://search.maven.org/remotecontent?filepath=jaxen/jaxen/1.1.3/jaxen-1.1.3.pom
declares those dependencies to be of type "plugin" )
On 14 Nov 2013, at 13:14, Jason Tesser wrote:
> I have the following POM http://
Looks like a JDK issue, because I can recreate it by just using 'javac'
( http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6391197 seems the closest
match )
As a workaround, move the "import pack.Prop;" line above the static import and
it should compile.
On 12 Nov 2013, at 11:51, Adrian Pana
Looking at the *MetadataSource components in the Maven source they're only
bound under:
org.apache.maven.artifact.metadata.ArtifactMetadataSource
and not:
org.apache.maven.repository.legacy.metadata.ArtifactMetadataSource
For example in MavenMetadataSource.java:
import
You can use requiresDependencyResolution (as Anders mentioned below) to choose
the initial scope of what gets populated into project.getArtifacts
You can also use maven-common-artifact-filters to filter those artifacts
further by scope, groupId, artifactId, etc:
http://maven.apache.org
Some related reports from 2011:
https://jira.codehaus.org/browse/MJAR-142
https://jira.codehaus.org/browse/MWAR-255
AFAICT the PlexusIoFileResource is effectively doing
setLastModified(file.lastModified()) to
https://github.com/sonatype/plexus-io/blob/master/src/main/j
On 3 Oct 2013, at 14:31, NRO wrote:
> Thanks for the clear explanation.
>
> All our artifacts are served by our Nexus Repository Manager (external and
> internal).
> All our repositories (hosted and proxy) are managed by Nexus, this is why
> our settings.xml and parent poms does not need to refer
The scenario described below fails for me with or without a mirror setting - as
I would expect it to.
Given a child project with a missing parent pom Maven will attempt to resolve
the parent given the available context, namely:
settings.xml
current pom.xml
Maven's super-
On 3 Oct 2013, at 11:11, Anders Hammar wrote:
> It should be the same for deps as well as parents. One difference could be
> if you have a repo declared in the pom (not setiings.xml). It might be that
> that repo is only used for deps and not the parent, I don't know.
FWIW, I've run some tests lo
orySystemUtils.newServiceLocator();
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=82b345e0094813b34fcac85e64dde2d5e02b4cc9
> Thanks,
> Bernd
>
> On Thu, 19 Sep 2013 23:52:20 +0200, Stuart McCulloch
> wrote:
>
>> Maven 3.1.0 was released after the Maven r
On 24 Sep 2013, at 01:31, Jamie Archibald wrote:
> I typically work behind a Nexus server at work which I use a settings.xml
> file. When I come home I remove the settings.xml from my m2 folder.
>
> As soon as I do this I can no longer resolve my maven dependencies that are
> my work modules, eve
Maven 3.1.0 was released after the Maven runtime project moved to git:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=summary
Specifically:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=tree;h=5a0e6574404b4964522d90c3438e25574a95466c;hb=893ca28a1da9d5f51ac03827af9
Wagon is trying to apply a given configuration, but it fails because it has a
property that doesn't exist in the chosen wagon provider.
Which version of Maven (and Wagon) are you using? Do you have a
httpConfiguration section in your settings.xml?
On 18 Sep 2013, at 21:37, Richard Sand wrote:
On 18 Sep 2013, at 15:09, Paul Benedict wrote:
> I believe this behavior is correct. IIRC, XML does not allow double-dashes
> inside a comment.
Specifically http://www.w3.org/TR/REC-xml/#sec-comments
"For compatibility, the string " -- " (double-hyphen) must not occur
within comments."
Since Maven3 this class is available in the maven-compat component:
http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22maven-compat%22
Note that plugins compiled against the old maven-artifact component should
still work with Maven3 (it gets translated
On 9 Jul 2013, at 18:47, Richard Sand wrote:
> Ah, simple solutions... :-)
>
> Now I'm onto the next similar problem, getting a JarArchiver. I'm getting 1)
> No implementation for org.codehaus.plexus.archiver.jar.JarArchiver was bound.
> In the 2.0 plugin I'm attempting to migrate, it has the c
On 3 Jul 2013, at 22:05, Mirko Friedenhagen wrote:
> Hello Robert,
>
> thanks for the quick answer, however I still get the same error :-(.
It looks like you have mismatched tags on line 27 of your components.xml:
org.apache.maven.plugins:maven-enforcer-plugin:enforce
> Regards Mirko
> --
>
On 2 Jul 2013, at 11:52, Salva Vilarrasa wrote:
> Hello,
> My name is Salva and are preparing some slides to give a technical
> presentation on Maven 3 and while preparing the slides i wanted to
> introduce the changes from Maven 2 to Maven 3 and the compatibility issues
> people may encounter but
I'm still unable to recreate this locally, even when using a project with
exactly the same layout/hierarchy as the one from that gist.
Does this happen when building from the command-line, or is there another
step involved? Such as building from an IDE or from CI?
On 30 May 2013 08:50, Simone Tr
Spring artifacts are deployed under a groupId of "org.springframework", not
"org.springsource":
http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.springframework%22
On 31 May 2013, at 22:17, Richard Vowles wrote:
> It does appear dead,
>
> http://repo1.maven.org/maven2/org/springso
On 31 May 2013, at 22:04, Loyall, David wrote:
> Hello.
>
> My maven installation has had some trouble downloading artifacts today.
>
> hobbes@metalbaby:~/scratch$ mvn
> org.apache.maven.plugins:maven-dependency-plugin:2.8:get
> -Dartifact=org.springsource:spring-jdbc:3.2.3.RELEA
gt; All the best,
> -Simo
>
> [1] https://gist.github.com/simonetripodi/5670183
>
> http://people.apache.org/~simonetripodi/
> http://twitter.com/simonetripodi
>
>
> On Wed, May 29, 2013 at 12:05 PM, Stuart McCulloch wrote:
>>
On 29 May 2013, at 10:49, Simone Tripodi wrote:
> Hi all mates,
>
> I am updating a set of old Maven plugins using Mvn3+Aether APIs, but
> unfortunately I am no longer able to run Mvn tests due to
> org.sonatype.guice.bean.reflect.Logs class cannot be found in the
> classpath, follows below the (
Have you tried restarting the affected slave? The remote class cache might be
holding onto an old/broken class.
On 12 Apr 2013, at 08:31, Johannes Pfeifer wrote:
> Hello Maven users,
>
> We use Maven and Jenkins to build our java products. Our builds broke the
> maven repositories yesterday,
On 11 Mar 2013, at 21:28, Thomas Koch wrote:
> Stuart McCulloch:
>> Perhaps you could post a link to your re-packaging build so people can
>> recreate the issue? There's not enough information here to debug the
>> problem remotely.
>
> http://anonscm.debian.org
On 8 Mar 2013, at 16:54, Thomas Koch wrote:
> Thomas Koch:
>> [DEBUG] Using 0 mojo extractors.
>
> I could track down the problem. The field "mojoDescriptorExtractors" in the
> DefaultMojoScanner class is not filed by plexus with the available extractors
> although they should be available on
On 1 February 2013 12:04, Martin Gainty wrote:
>
> Stuart
> Yes i agree that the PluginManager *should* be discovering the implementor
> at for Java class but instead pulls in
> AbstractModelloGeneratorMojo which extends AbstractMojo
>
Remember to attach your test project that demonstrates the
On 31 January 2013 21:29, Martin Gainty wrote:
>
> Gentlemen
> I found a consistent bug with PluginManager not able to locate @goal/** *
> artifactId=modello-maven-plugin
> * @author mailto:tryg...@inamo.no";>Trygve Laugstøl
> * @version 1.5
> * @threadSafe
> */
> public abstract class Abstra
On 5 Nov 2012, at 09:30, Stadelmann Josef wrote:
> my svn trunk update has
> Completed: At revision: 1405720
>
> using maven 3.0.5-snapshot to build maven 3.1-snapshot
Any particular reason why you're using one unreleased snapshot to build a
different snapshot?
> it always fails when buildi
OK - we sit behind a firewall , if that makes a difference?
The bootstrap build should use your local settings.xml just like Maven, so as
long this is configured with any proxy needed to access Maven Central then it
should be fine.
> Josef
>
> -Ursprüngliche Nachricht-
>
On 1 November 2012 10:29, Stadelmann Josef <
josef.stadelm...@axa-winterthur.ch> wrote:
> How can I cure best the problems shown below? it occurs during a
> bootstrap-build of maven-3/trunk on my Vista System.
> (see red lines, which are of interesst to me).
>
> I have successfully build from sour
On 4 Oct 2012, at 19:22, Davis Ford wrote:
> This doesn't make a whole lot of sense to me. Any idea what the problem is
> here?
You've given the jersey-server dependency a scope of "runtime" which means it
is on the runtime and test classpaths, but _not_ the compile classpath,
therefore the cl
Bugs can be reported on the github site: https://github.com/bndtools/bnd or via
the Apache Felix project. You should also try the latest 2.4.0-SNAPSHOT of the
bundleplugin, as this uses the latest bndlib code which is expected to be
released soon.
--
Cheers, Stuart
On 21 Sep 2012, at 01:04, Ma
On 12 Aug 2012, at 03:54, Wayne Fay wrote:
>> I'm also using the Apache Felix bundle-plugin which allows for:
>>
>>bundle
>
> This is not a packaging delivered by Apache Maven. Thus you can
> "blame" whoever is making this packaging available to you.
>
>> That is, I can use either or o
On 27 July 2012 14:05, Matthias Pfeifer wrote:
> Hello,
>
> I have a jar file that i plan to add to a projects dependencies. I
> need to test this jar file as a dependency of some project and
> therefore did
>
> $ mvn -l mvn.log -e -X install:install-file -Dfile=myartifact.jar
> -DgroupId=com.myc
l me why the compiler won't display the full error message?
probably related to http://jira.codehaus.org/browse/MCOMPILER-158
> W dniu 2012-07-16 15:03, Stuart McCulloch pisze:
>> Also be aware of an issue using JDK7 to compile against the official OSGi
>> 4.3 API jars...
>
Also be aware of an issue using JDK7 to compile against the official OSGi 4.3
API jars...
http://stackoverflow.com/questions/10911231/how-to-compile-mavenized-osgi-4-3-bundle-with-openjdk-7
Solutions are to either use JDK6, or use the recently released OSGi 5.0 API
jars, or rebuild the 4.3
n't expect many proxies to be generated with Maven - they're
typically only used when there are circular references between constructors.
> Proxies are also loaded via the ClassLoader and consume perm gen space.
>
> LieGrue,
> strub
>
> - Original Message -
&
1 - 100 of 234 matches
Mail list logo
