> From: [email protected]
> Date: Wed, 26 Feb 2014 12:26:48 +0100
> Subject: Re: Google Summer of Code - Java opportunity, mentors needed
> To: [email protected]
>
> While Benson is right about -source artifacts (not meant for rebuilding),
> this resembles me to M2E's "Project
>Materialisation", where based on POM of
> the given project (is fetched during dependency resolution), and IF the SCM
> metadata are okay, etc, the project tag is checked out into workspace....
>
MG>In which case we would need a standard way for SCM Metadata / Project Tag
checked out into IDE:
MG>Eclipse?
MG>Idea?
MG>NetBeans?
>
MG>Concrete Example I need this nexus-plugin to work:
MG>2014-02-04 0 8:41:18 WARN [pxpool-1-thread-2] admin
org.sonatype.scheduling.DefaultScheduledTask - Excein in call method of
scheduled task Closing staging repositories:
[stagingprofileformartinplugin-1002]
java.lang.IllegalStateException: No rule evaluator configured for type:
MartinPluginRuleType
at com.google.common.base.Preconditions.checkState(Preconditions.java:176)
~[guava-14.0.1.jar:na]
at
com.sonatype.nexus.staging.internal.rules.DefaultStagingRuleFactory.createStagingRule(DefaultStagingRuleFactory.java:90)
~[na:na]
at
com.sonatype.nexus.staging.internal.StagingRulesHelper.evaluateRuleSet(StagingRulesHelper.java:216)
~[na:na]
at
com.sonatype.nexus.staging.internal.StagingRulesHelper.evaluateProfileRuleSets(StagingRulesHelper.java:133)
~[na:na]
at
com.sonatype.nexus.staging.internal.StagingRulesHelper.evaluate(StagingRulesHelper.java:104)
~[na:na]
at
com.sonatype.nexus.staging.internal.task.RepositoryCloseTask$CloseOperation.verifyItem(RepositoryCloseTask.java:90)
~[na:na]
at
com.sonatype.nexus.staging.internal.task.RepositoryCloseTask$CloseOperation.verifyItem(RepositoryCloseTask.java:1)
~[na:na]
at
com.sonatype.nexus.staging.internal.task.OperationTaskSupport$OperationSupport.verify(OperationTaskSupport.java:295)
~[na:na]
at
com.sonatype.nexus.staging.internal.task.OperationTaskSupport.executeOperations(OperationTaskSupport.java:426)
~[na:na]
at
com.sonatype.nexus.staging.internal.task.OperationTaskSupport.doCall(OperationTaskSupport.java:416)
~[na:na]
at
com.sonatype.nexus.staging.internal.task.TaskSupport.call(TaskSupport.java:38)
~[na:na]
at
com.sonatype.nexus.staging.internal.task.StagingTaskSupport.call(StagingTaskSupport.java:134)
~[na:na]
at
com.sonatype.nexus.staging.internal.task.StagingBackgroundTask.execute(StagingBackgroundTask.java:68)
~[na:na]
at
com.sonatype.nexus.staging.internal.task.NexusTaskSupport.doRun(NexusTaskSupport.java:53)
~[na:na]
at
com.sonatype.nexus.staging.internal.task.NexusTaskSupport.doRun(NexusTaskSupport.java:1)
~[na:na]
at
org.sonatype.nexus.scheduling.AbstractNexusTask.call(AbstractNexusTask.java:157)
~[nexus-core-2.7.2-03.jar:2.7.2-03]
at
org.sonatype.scheduling.DefaultScheduledTask.call(DefaultScheduledTask.java:419)
~[nexus-scheduler-2.7.2-03.jar:2.7.2-03]
at org.sonatype.nexus.threads.MDCAwareCallable.call(MDCAwareCallable.java:45)
~[nexus-core-2.7.2-03.jar:2.7.2-03]
at
org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)
~[shiro-core-1.2.2.jar:1.2.2]
at
org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)
~[shiro-core-1.2.2.jar:1.2.2]
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) ~[na:1.7.0_25]
at java.util.concurrent.FutureTask.run(Unknown Source) ~[na:1.7.0_25]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown
Source) ~[na:1.7.0_25]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
Source) ~[na:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
~[na:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
~[na:1.7.0_25]
at java.lang.Thread.run(Unknown Source) ~[na:1.7.0_25]
MG>Q1: Can I get Sonatype source code to debug Nexus?
MG>Q2: Could I use maven-to-idea-plugin to pull source into IDEA ?
MG>Q3: Should I care about -P -D options or is this not appropriate use of
Profile/SystemProperty?
MG>I am thinking I will need Maven-4 to solve this problem
>
> On Wed, Feb 26, 2014 at 12:20 PM, Benson Margulies
> <[email protected]>wrote:
>
> > I don't believe that this is a viable scheme.
> >
> > Maven source artifacts are not generally buildable, but are aimed at
> > IDEs for debugging visibility. You can't trust the SVM info, and you
> > don't know what -P/-D options were used to make the binary. We would
> > need a new train of metadata. This will only lead to more of the
> > horrible pattern of distro people mis-building Maven and Maven
> > artifacts, leading to confused users and bug reports when they expect
> > these things to work right. Maven was not designed to facilitate the
> > Debian pattern. If someone wants to move in that direction, they
> > should join the dev community, watch for work on Maven 4, and advocate
> > (and volunteer to code) solutions to provide the right metadata to do
> > this. Thowing an inexperienced student into trying to do this with
> > Maven 3 in a summer is a recipe for failure.
> >
> > On Tue, Feb 25, 2014 at 4:48 AM, Daniel Pocock <[email protected]>
> > wrote:
> > >
> > >
> > > Hi,
> > >
> > > I recently published an idea for discovering the source code of Java
> > > projects (e.g. by exploring meta data from pom.xml) and trying to
> > > automatically and recursively build dependencies (including plugins)
> > > from source
> > >
> > >
> > https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FRecursively_building_Java_dependencies_from_source.Recursively_building_Java_dependencies_from_source
> > >
> > > This would satisfy various objectives, for example:
> > >
> > > - automated construction of Debian/Ubuntu/RPM packages
> > > - ensuring that non-free components don't creep into the dependency tree
> > > of projects that aim to be published under a free license
> > > - ensuring that 100% of dependency code can be passed through code
> > > quality/security scanning tools (this is a common requirement for larger
> > > corporations when evaluating whether to use a free software project)
> > >
> > > I have some plans for how this project could be broken down into
> > > achievable tasks for a GSoC student but to go ahead it would need at
> > > least one additional mentor, mainly because Google has accepted the
> > > Ganglia organisation this year and I am one of the admins for Ganglia.
> > > The project has been proposed under Debian (mainly as a way of enabling
> > > the creation of more Debian packages) but it could also be completed
> > > under another organisation. Please feel free to email me privately if
> > > you may be interested.
> > >
> > > Regards,
> > >
> > > Daniel
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
