Re: svn commit: r1799189 - /maven/plugins/trunk/maven-assembly-plugin/pom.xml

[Guillaume Boué]

Hi,

The unit test 
AssemblyProxyArchiverTest#addDirectory_NoPerms_CallAcceptFilesOnlyOnce 
is failing with this commit, and I can reproduce the failure on Ubuntu 
with OpenJDK 7. It turns out to be coming from conflicting plexus-io 
dependencies:


- The plugin now depends on a JDK 7 version of plexus-io (3.0.0).
- But the plugin also depends on plexus-archiver 3.4, which depends on a 
JDK 6 version plexus-io (2.7.1).


Some plexus-io classes that were used reflectively in plexus-archiver 
(when JDK 7 is used), like Java7Reflector, are thus missing now, since 
they were removed in plexus-io 3.0.0. This explains the 
NoClassDefFoundError in the unit test. I noticed Plexus Archiver trunk 
has moved to JDK 7 also, so we'll need to upgrade to plexus-archiver 3.5 
as soon as possible.


Guillaume


Le 19/06/2017 à 14:18, micha...@apache.org a écrit :

Author: michaelo
Date: Mon Jun 19 12:18:42 2017
New Revision: 1799189

URL: http://svn.apache.org/viewvc?rev=1799189=rev
Log:
[MASSEMBLY-859] Upgrade to Plexus IO 3.0.0

This closes #117

Modified:
 maven/plugins/trunk/maven-assembly-plugin/pom.xml

Modified: maven/plugins/trunk/maven-assembly-plugin/pom.xml
URL: 
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-assembly-plugin/pom.xml?rev=1799189=1799188=1799189=diff
==
--- maven/plugins/trunk/maven-assembly-plugin/pom.xml (original)
+++ maven/plugins/trunk/maven-assembly-plugin/pom.xml Mon Jun 19 12:18:42 2017
@@ -157,7 +157,7 @@ under the License.
  
org.codehaus.plexus
plexus-io
-  2.7.1
+  3.0.0
  
  
org.apache.maven





---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Migration of remaining plugins to Git

[Paul Hammant]

I think the plugins are descoped for a while.

How about  https://github.com/apache-maven/ ?

Luckily GitHub does 302s just find if things get renamed or moved between
orgs.

- Paul

On Mon, Jun 19, 2017 at 3:34 PM, Bindul Bhowmik 
wrote:

> Paul,
>
> On Mon, Jun 19, 2017 at 12:42 PM, Paul Hammant  wrote:
> > Back from Github's suggestions team: "Currently, we don't have the
> ability
> > to group repos beyond the organization level, but I'll definitely
> consider
> > this a feature request."
>
> Until such time, how about grouping the repositories by name, like
> https://github.com/apache/maven-plugin-
>
> A number of other projects in Apache have done this, for example
> https://git-wip-us.apache.org/repos/asf?a=project_list=
> incubator-predictionio
> or https://gitbox.apache.org/repos/asf?a=project_list=
> incubator-openwhisk
>
> - Bindul
>
> >
> > - Paul
> >
> > On Sun, Jun 18, 2017 at 7:04 PM, Paul Hammant  wrote:
> >>
> >> I met Chris Wanstrath at a meetup in Cincinatti about four years ago,
> and
> >> bent his ear about how fantastic Github-Pages (and Jekyll) was as a
> CMS. I
> >> suggested that if they could add themes for "high school", "community
> >> group", etc they could pull in another category of user of the
> platform, and
> >> that the themes that are available for gh-pages are not that useful as
> they
> >> are.
> >>
> >>
> >>
> >> ^ screencap from today: unchanged :(
> >>
> >> On Sun, Jun 18, 2017 at 6:46 PM, Stephen Connolly
> >>  wrote:
> >>>
> >>> Polite, yes, just non commital ;-)
> >>>
> >>> On Sun 18 Jun 2017 at 23:10, Paul Hammant  wrote:
> >>>
> >>> > They're always very polite for things that I ask for, but I can't
> claim
> >>> > to
> >>> > have suggested anything that got implemented. I've a better hit-rate
> >>> > with
> >>> > JetBrains and their IDEs.
> >>> >
> >>> > - Paul
> >>> >
> >>> > On Sun, Jun 18, 2017 at 4:39 PM, Stephen Connolly <
> >>> > stephen.alan.conno...@gmail.com> wrote:
> >>> >
> >>> > > Liable to get an answer like:
> >>> > >
> >>> > > > We don't comment our roadmap publicly I'm afraid
> >>> > >
> >>> > > (I've gotten that a couple of times for different things... you'd
> >>> > > think
> >>> > > given that I'm the maintainer of the GitHub Branch Source plugin
> for
> >>> > > Jenkins they might - you know - want to help... but alas)
> >>> > >
> >>> > > On 18 June 2017 at 10:12, Paul Hammant  wrote:
> >>> > >
> >>> > > > Good thought. We could ask about a timeline.
> >>> > > >
> >>> > > > On Sun, Jun 18, 2017 at 1:00 PM, Stephen Connolly <
> >>> > > > stephen.alan.conno...@gmail.com> wrote:
> >>> > > >
> >>> > > > > They are now adding user grouping... I wonder how long before
> >>> > > > > repo
> >>> > > > grouping
> >>> > > > > too
> >>> > > > >
> >>> > > > > On Sun 18 Jun 2017 at 17:12, Paul Hammant 
> >>> > > > > wrote:
> >>> > > > >
> >>> > > > > > Choose one to start with, is what I would do.
> >>> > > > > >
> >>> > > > > > git svn clone of a trunk only, then make that master.
> >>> > > > > > branch/tag
> >>> > > > history
> >>> > > > > > can be retained in Subversion but also up on MavenCentral as
> >>> > > > > > foo-x.y-sources.jar files.  Unless you optimize that
> >>> > > > > > git-svn-clone
> >>> > > > > > operation by specifying the first Svn commit for the module
> in
> >>> > > > question,
> >>> > > > > > it'll need many hours to iterate over all commits to pluck
> out
> >>> > > > > > the
> >>> > > ones
> >>> > > > > > pertinent to the trunk of that module.
> >>> > > > > >
> >>> > > > > > GitHub only allows a single effective 'parent directory' for
> >>> > > > > > repos,
> >>> > > so
> >>> > > > > > instead of the general github.com/apache org (and in lieu of
> >>> > > > > > github.com/apache/maven/ which is what you'd
> >>> > > > > > actually
> >>> > > > want),
> >>> > > > > we
> >>> > > > > > could do github.com/apache-maven/.
> >>> > > > > >
> >>> > > > > > I volunteer for some of the work.  Err, maybe I should read
> >>> > > > > > those
> >>> > > > > > confluence pages.
> >>> > > > > >
> >>> > > > > > - Paul
> >>> > > > > >
> >>> > > > > >
> >>> > > > > >
> >>> > > > > > On Sun, Jun 18, 2017 at 11:51 AM, Hervé BOUTEMY <
> >>> > > herve.bout...@free.fr
> >>> > > > >
> >>> > > > > > wrote:
> >>> > > > > >
> >>> > > > > > > yes, git is really ubiquitous now and nowadays could
> perhaps
> >>> > > > > > > help
> >>> > > > some
> >>> > > > > > > contributions
> >>> > > > > > > here is our tracking of git migration [1]
> >>> > > > > > >
> >>> > > > > > > there are a few entries that we could move if someone takes
> >>> > > > > > > the
> >>> > > job:
> >>> > > > > > > Doxia core, Doxia Site Tools, Enforcer, Jxr, Plugin Tools,
> >>> > Release
> >>> > > > > > >
> >>> > > > > > > there are issues to fix when migrating 1 svn repo
> >>> > > (trunk/tags/branch)
> >>> > > > > to
> >>> > > > > > > many
> >>> 

Re: Migration of remaining plugins to Git

[Bindul Bhowmik]

Paul,

On Mon, Jun 19, 2017 at 12:42 PM, Paul Hammant  wrote:
> Back from Github's suggestions team: "Currently, we don't have the ability
> to group repos beyond the organization level, but I'll definitely consider
> this a feature request."

Until such time, how about grouping the repositories by name, like
https://github.com/apache/maven-plugin-

A number of other projects in Apache have done this, for example
https://git-wip-us.apache.org/repos/asf?a=project_list=incubator-predictionio
or https://gitbox.apache.org/repos/asf?a=project_list=incubator-openwhisk

- Bindul

>
> - Paul
>
> On Sun, Jun 18, 2017 at 7:04 PM, Paul Hammant  wrote:
>>
>> I met Chris Wanstrath at a meetup in Cincinatti about four years ago, and
>> bent his ear about how fantastic Github-Pages (and Jekyll) was as a CMS. I
>> suggested that if they could add themes for "high school", "community
>> group", etc they could pull in another category of user of the platform, and
>> that the themes that are available for gh-pages are not that useful as they
>> are.
>>
>>
>>
>> ^ screencap from today: unchanged :(
>>
>> On Sun, Jun 18, 2017 at 6:46 PM, Stephen Connolly
>>  wrote:
>>>
>>> Polite, yes, just non commital ;-)
>>>
>>> On Sun 18 Jun 2017 at 23:10, Paul Hammant  wrote:
>>>
>>> > They're always very polite for things that I ask for, but I can't claim
>>> > to
>>> > have suggested anything that got implemented. I've a better hit-rate
>>> > with
>>> > JetBrains and their IDEs.
>>> >
>>> > - Paul
>>> >
>>> > On Sun, Jun 18, 2017 at 4:39 PM, Stephen Connolly <
>>> > stephen.alan.conno...@gmail.com> wrote:
>>> >
>>> > > Liable to get an answer like:
>>> > >
>>> > > > We don't comment our roadmap publicly I'm afraid
>>> > >
>>> > > (I've gotten that a couple of times for different things... you'd
>>> > > think
>>> > > given that I'm the maintainer of the GitHub Branch Source plugin for
>>> > > Jenkins they might - you know - want to help... but alas)
>>> > >
>>> > > On 18 June 2017 at 10:12, Paul Hammant  wrote:
>>> > >
>>> > > > Good thought. We could ask about a timeline.
>>> > > >
>>> > > > On Sun, Jun 18, 2017 at 1:00 PM, Stephen Connolly <
>>> > > > stephen.alan.conno...@gmail.com> wrote:
>>> > > >
>>> > > > > They are now adding user grouping... I wonder how long before
>>> > > > > repo
>>> > > > grouping
>>> > > > > too
>>> > > > >
>>> > > > > On Sun 18 Jun 2017 at 17:12, Paul Hammant 
>>> > > > > wrote:
>>> > > > >
>>> > > > > > Choose one to start with, is what I would do.
>>> > > > > >
>>> > > > > > git svn clone of a trunk only, then make that master.
>>> > > > > > branch/tag
>>> > > > history
>>> > > > > > can be retained in Subversion but also up on MavenCentral as
>>> > > > > > foo-x.y-sources.jar files.  Unless you optimize that
>>> > > > > > git-svn-clone
>>> > > > > > operation by specifying the first Svn commit for the module in
>>> > > > question,
>>> > > > > > it'll need many hours to iterate over all commits to pluck out
>>> > > > > > the
>>> > > ones
>>> > > > > > pertinent to the trunk of that module.
>>> > > > > >
>>> > > > > > GitHub only allows a single effective 'parent directory' for
>>> > > > > > repos,
>>> > > so
>>> > > > > > instead of the general github.com/apache org (and in lieu of
>>> > > > > > github.com/apache/maven/ which is what you'd
>>> > > > > > actually
>>> > > > want),
>>> > > > > we
>>> > > > > > could do github.com/apache-maven/.
>>> > > > > >
>>> > > > > > I volunteer for some of the work.  Err, maybe I should read
>>> > > > > > those
>>> > > > > > confluence pages.
>>> > > > > >
>>> > > > > > - Paul
>>> > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > > > On Sun, Jun 18, 2017 at 11:51 AM, Hervé BOUTEMY <
>>> > > herve.bout...@free.fr
>>> > > > >
>>> > > > > > wrote:
>>> > > > > >
>>> > > > > > > yes, git is really ubiquitous now and nowadays could perhaps
>>> > > > > > > help
>>> > > > some
>>> > > > > > > contributions
>>> > > > > > > here is our tracking of git migration [1]
>>> > > > > > >
>>> > > > > > > there are a few entries that we could move if someone takes
>>> > > > > > > the
>>> > > job:
>>> > > > > > > Doxia core, Doxia Site Tools, Enforcer, Jxr, Plugin Tools,
>>> > Release
>>> > > > > > >
>>> > > > > > > there are issues to fix when migrating 1 svn repo
>>> > > (trunk/tags/branch)
>>> > > > > to
>>> > > > > > > many
>>> > > > > > > git repos that are documented but not solved yet
>>> > > > > > > Plugins and shared components are the 2 big repos, with
>>> > > respectively
>>> > > > 41
>>> > > > > > > and 26
>>> > > > > > > parts if we switch to git that look hard to manage if we
>>> > > > > > > don't
>>> > > have a
>>> > > > > > plan.
>>> > > > > > > Perphaps Jenkins pipelines could provide some solutions on
>>> > > > > > > the
>>> > > > Jenkins
>>> > > > > > > side.
>>> > > > > > >
>>> > > > > > > Skins is perhaps not an issue any more now that we 

Re: Migration of remaining plugins to Git

[Paul Hammant]

Back from Github's suggestions team: "Currently, we don't have the ability
to group repos beyond the organization level, but I'll definitely consider
this a feature request."

- Paul

On Sun, Jun 18, 2017 at 7:04 PM, Paul Hammant  wrote:

> I met Chris Wanstrath at a meetup in Cincinatti about four years ago, and
> bent his ear about how fantastic Github-Pages (and Jekyll) was as a CMS. I
> suggested that if they could add themes for "high school", "community
> group", etc they could pull in another category of user of the platform,
> and that the themes that are available for gh-pages are not that useful as
> they are.
>
> [image: Inline image 1]
>
> ^ screencap from today: unchanged :(
>
> On Sun, Jun 18, 2017 at 6:46 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> Polite, yes, just non commital ;-)
>>
>> On Sun 18 Jun 2017 at 23:10, Paul Hammant  wrote:
>>
>> > They're always very polite for things that I ask for, but I can't claim
>> to
>> > have suggested anything that got implemented. I've a better hit-rate
>> with
>> > JetBrains and their IDEs.
>> >
>> > - Paul
>> >
>> > On Sun, Jun 18, 2017 at 4:39 PM, Stephen Connolly <
>> > stephen.alan.conno...@gmail.com> wrote:
>> >
>> > > Liable to get an answer like:
>> > >
>> > > > We don't comment our roadmap publicly I'm afraid
>> > >
>> > > (I've gotten that a couple of times for different things... you'd
>> think
>> > > given that I'm the maintainer of the GitHub Branch Source plugin for
>> > > Jenkins they might - you know - want to help... but alas)
>> > >
>> > > On 18 June 2017 at 10:12, Paul Hammant  wrote:
>> > >
>> > > > Good thought. We could ask about a timeline.
>> > > >
>> > > > On Sun, Jun 18, 2017 at 1:00 PM, Stephen Connolly <
>> > > > stephen.alan.conno...@gmail.com> wrote:
>> > > >
>> > > > > They are now adding user grouping... I wonder how long before repo
>> > > > grouping
>> > > > > too
>> > > > >
>> > > > > On Sun 18 Jun 2017 at 17:12, Paul Hammant 
>> wrote:
>> > > > >
>> > > > > > Choose one to start with, is what I would do.
>> > > > > >
>> > > > > > git svn clone of a trunk only, then make that master. branch/tag
>> > > > history
>> > > > > > can be retained in Subversion but also up on MavenCentral as
>> > > > > > foo-x.y-sources.jar files.  Unless you optimize that
>> git-svn-clone
>> > > > > > operation by specifying the first Svn commit for the module in
>> > > > question,
>> > > > > > it'll need many hours to iterate over all commits to pluck out
>> the
>> > > ones
>> > > > > > pertinent to the trunk of that module.
>> > > > > >
>> > > > > > GitHub only allows a single effective 'parent directory' for
>> repos,
>> > > so
>> > > > > > instead of the general github.com/apache org (and in lieu of
>> > > > > > github.com/apache/maven/ which is what you'd
>> actually
>> > > > want),
>> > > > > we
>> > > > > > could do github.com/apache-maven/.
>> > > > > >
>> > > > > > I volunteer for some of the work.  Err, maybe I should read
>> those
>> > > > > > confluence pages.
>> > > > > >
>> > > > > > - Paul
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > On Sun, Jun 18, 2017 at 11:51 AM, Hervé BOUTEMY <
>> > > herve.bout...@free.fr
>> > > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > yes, git is really ubiquitous now and nowadays could perhaps
>> help
>> > > > some
>> > > > > > > contributions
>> > > > > > > here is our tracking of git migration [1]
>> > > > > > >
>> > > > > > > there are a few entries that we could move if someone takes
>> the
>> > > job:
>> > > > > > > Doxia core, Doxia Site Tools, Enforcer, Jxr, Plugin Tools,
>> > Release
>> > > > > > >
>> > > > > > > there are issues to fix when migrating 1 svn repo
>> > > (trunk/tags/branch)
>> > > > > to
>> > > > > > > many
>> > > > > > > git repos that are documented but not solved yet
>> > > > > > > Plugins and shared components are the 2 big repos, with
>> > > respectively
>> > > > 41
>> > > > > > > and 26
>> > > > > > > parts if we switch to git that look hard to manage if we don't
>> > > have a
>> > > > > > plan.
>> > > > > > > Perphaps Jenkins pipelines could provide some solutions on the
>> > > > Jenkins
>> > > > > > > side.
>> > > > > > >
>> > > > > > > Skins is perhaps not an issue any more now that we deprecated
>> 3
>> > old
>> > > > > > skins,
>> > > > > > > then only 2 skins remain. Pom would be feasible now that I
>> > reworked
>> > > > > Maven
>> > > > > > > parent poms to be only in one global release: just the history
>> > > > > migration
>> > > > > > > could
>> > > > > > > be tricky given this exact rework :)
>> > > > > > >
>> > > > > > >
>> > > > > > > Then we can move forward:
>> > > > > > > - just do it for some svn repos
>> > > > > > > - a plan, particularly on Jenkins side, has to be found for
>> > plugins
>> > > > and
>> > > > > > > shared
>> > > > > > >
>> > > > > > > any taker for some of the work?
>> > > > > > >
>> > > > > > > Regards,
>> > > > > > >
>> 

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

[Robert Scholte]

On Mon, 19 Jun 2017 13:21:22 +0200, Enrico Olivelli   
wrote:



Karl,
I am getting this error using maven site plugin 3.6 and jdk 9-ea+174

java.lang.reflect.InaccessibleObjectException: Unable to make
protected final java.lang.Class
java.lang.ClassLoader.findLoadedClass(java.lang.String) accessible:
module java.base does not "opens java.lang" to unnamed  module
@7069f076

at java.base/java.lang.reflect.Method.setAccessible(Method.java:192)
at  
org.parboiled.transform.AsmUtils.findLoadedClass(AsmUtils.java:206)


there is an issue already opened by Robert
https://github.com/sirthias/parboiled/issues/104


This issue won't be fixed because parboiled is not maintained anymore.  
Doxia-pegdown should switch to flexmark-java[1]


Robert

[1] https://issues.apache.org/jira/browse/DOXIA-553



the error is different from yours

-- Enrico

this is the full stacktrace

...Caused by: java.lang.ExceptionInInitializerError
at  
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native

Method)
at  
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at  
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at  
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)
at  
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86)
at  
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
at  
com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
at  
com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:89)
at  
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115)
at  
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:133)
at  
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
at  
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:87)
at  
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267)
at  
com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)
at  
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103)
at  
com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)
at  
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051)
at  
org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
at  
com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81)
at  
com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:53)
at  
com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:65)
at  
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115)
at  
org.eclipse.sisu.bean.BeanScheduler$CycleActivator.onProvision(BeanScheduler.java:230)
at  
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:126)
at  
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
at  
com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:63)
at  
com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:45)
at  
com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at  
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103)
at  
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at  
com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)
at  
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at  
com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)
at  
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)
at  
com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)
at  
org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:81)
at  
org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51)

at java.base/java.util.AbstractMap.get(AbstractMap.java:187)
at  
org.apache.maven.doxia.parser.manager.DefaultParserManager.getParser(DefaultParserManager.java:46)
at  

[GitHub] maven-plugins pull request #116: Upgrade to Java 7

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/maven-plugins/pull/116


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-plugins pull request #117: Upgrade to Plexus IO 3.0.0

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/maven-plugins/pull/117


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

[Enrico Olivelli]

Karl,
I am getting this error using maven site plugin 3.6 and jdk 9-ea+174

java.lang.reflect.InaccessibleObjectException: Unable to make
protected final java.lang.Class
java.lang.ClassLoader.findLoadedClass(java.lang.String) accessible:
module java.base does not "opens java.lang" to unnamed  module
@7069f076

at java.base/java.lang.reflect.Method.setAccessible(Method.java:192)
at org.parboiled.transform.AsmUtils.findLoadedClass(AsmUtils.java:206)

there is an issue already opened by Robert
https://github.com/sirthias/parboiled/issues/104

the error is different from yours

-- Enrico

this is the full stacktrace

...Caused by: java.lang.ExceptionInInitializerError
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)
at 
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86)
at 
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
at 
com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
at 
com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:89)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:133)
at 
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
at 
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:87)
at 
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267)
at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)
at 
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103)
at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)
at 
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051)
at 
org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
at 
com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81)
at 
com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:53)
at 
com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:65)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115)
at 
org.eclipse.sisu.bean.BeanScheduler$CycleActivator.onProvision(BeanScheduler.java:230)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:126)
at 
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
at 
com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:63)
at 
com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:45)
at 
com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at 
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103)
at 
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)
at 
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)
at 
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)
at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)
at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:81)
at org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51)
at java.base/java.util.AbstractMap.get(AbstractMap.java:187)
at 
org.apache.maven.doxia.parser.manager.DefaultParserManager.getParser(DefaultParserManager.java:46)
at org.apache.maven.doxia.DefaultDoxia.getParser(DefaultDoxia.java:72)
at 
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:367)
at 
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
at 
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)

[GitHub] maven-plugins pull request #118: help me to do this??

[narmusekar]

GitHub user narmusekar opened a pull request:

https://github.com/apache/maven-plugins/pull/118

help me to do this??

i want to build a netty server that accepts json object to store the data 
in a queue can anybody help me???

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/narmusekar/maven-plugins patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugins/pull/118.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #118


commit 139a63793221a9a50d4d31ee6a4e265deaddf4fb
Author: narmusekar 
Date:   2017-06-19T10:40:18Z

i want to build a netty server that accepts json object to store the data 
in a queue can anybody help me???




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-plugins pull request #115: Upgrade to Plexus Archiver 3.5-SNAPSHOT

[snicoll]

Github user snicoll closed the pull request at:

https://github.com/apache/maven-plugins/pull/115


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-plugins pull request #117: Upgrade to Plexus IO 3.0.0

[snicoll]

GitHub user snicoll opened a pull request:

https://github.com/apache/maven-plugins/pull/117

Upgrade to Plexus IO 3.0.0

See MASSEMBLY-859

PR #116 should be merged first as plexus io 3.0.0 requires Java 7

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/snicoll/maven-plugins MASSEMBLY-859

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugins/pull/117.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #117


commit 32c7570a3e8c1aa99e0ebf8a792136bca729b7f1
Author: Stephane Nicoll 
Date:   2017-06-19T09:23:24Z

[MASSEMBLY-859] Upgrade to Plexus IO 3.0.0




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-plugins pull request #116: Upgrade to Java 7

[snicoll]

GitHub user snicoll opened a pull request:

https://github.com/apache/maven-plugins/pull/116

Upgrade to Java 7

See MASSEMBLY-860

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/snicoll/maven-plugins MASSEMBLY-860

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugins/pull/116.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #116


commit 549b9d9ef49e0f663cc6b847fa457d47452d1938
Author: Stephane Nicoll 
Date:   2017-06-19T09:19:57Z

[MASSEMBLY-860] Upgrade to Java 7




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org