Am 17.03.2013 18:22, schrieb Jeff MAURY:
Impress to see that you're claiming you personal priorities prevent you to
open a ticket on JIRA but allow you to write a mail including external
links
The same question could go to Anders...
Joachim, you're way out of line here! Please do a background check on my
contribution to this project before you insult me!
On Mon, Mar 18, 2013 at 7:04 AM, Joachim Durchholz j...@durchholz.org wrote:
Am 17.03.2013 18:22, schrieb Jeff MAURY:
Impress to see that you're claiming you personal
Am 18.03.2013 07:43, schrieb Anders Hammar:
Joachim, you're way out of line here! Please do a background check on my
contribution to this project before you insult me!
Anders, your contributions to Maven were never part of this discussion.
Except if you base your demands on how your
Leave it seems to be the option most often chosen. Having just
joined this mailing list, I'm beginning to suspect why.
On 3/17/13, Joachim Durchholz j...@durchholz.org wrote:
Am 18.03.2013 07:43, schrieb Anders Hammar:
Joachim, you're way out of line here! Please do a background check on my
Am 18.03.2013 06:56, schrieb Kevin Krumwiede:
Are the jars produced by maven-source-plugin intended primarily as a
reference for IDEs and other automated tools, as opposed to being
something you would actually build from?
They are intended primarily as a reference thing.
I ask because I have
They are intended primarily as a reference thing.
That's the answer I was hoping for. Thanks!
On 3/18/13, Tim Kettler tim.kett...@udo.edu wrote:
Am 18.03.2013 06:56, schrieb Kevin Krumwiede:
Are the jars produced by maven-source-plugin intended primarily as a
reference for IDEs and other
On Mon, Mar 18, 2013 at 6:56 AM, Kevin Krumwiede kjk...@gmail.com wrote:
If the -sources jar is only intended as a reference, then I want to
exclude the generated sources and resources.
Why would you do that?
In addition to reading the code right from the IDE rather than
switching to GitHub or
I would not base your opinion on this one thread.
Joachim got off on the wrong foot by mistaking us trying to guide him
towards a path (where he won't fight maven all the way) for us being
evangelical and spouting religious dogma... Some of us in this list may
have egged on the troll vs troll
Barrie, the stats for all maven artifacts are available to maven
committers by logging in to the https://repository.apache.org instance
and clicking on Central Stats
On Thu, Mar 14, 2013 at 9:06 PM, Barrie Treloar baerr...@gmail.com wrote:
Hi,
I am writing my first custom plugin for maven.
I`m now facing 2 problem.
- I need to know the absolute location of every dependency (incl.
transitive deps)
- Is there a solution for workspace dependencies (i would like to have a
jar of them as well) like disable workspace resolution as a
I would start by describing what you want to do and why. That way we can
determine if you approach fits best with the maven way and suggest the
best way to align with that... There are some alarm bells ringing
On Monday, 18 March 2013, Jan Engler wrote:
Hi,
I am writing my first custom plugin
Ok,
I am adapting the jni4net maven plugin (see
https://code.google.com/p/jni4net/) to fit our needs. In short, this
plugin collects a set of classes with the intention to generate .net
wrapper for. Furthermore, the tool that create those wrappers
(proxygen.exe) needs the complete
Hi,
I am setting up a new project with Maven.
The build task is as follows:
For each top level folder (package) under the
${project.build.directory}, zip up all the files under the folder.
Please note there is NO compilation or build required, just zip up
folders...
Try project.getCompileClasspathElements(), it resolves transitive
dependencies and gives you their location as absolute file names.
http://maven.apache.org/ref/3.0.5/maven-core/apidocs/org/apache/maven/project/MavenProject.html#getCompileClasspathElements()
On Mon, Mar 18, 2013 at 2:22 PM, Jan
Hi all,
In a pom using a custom plugin I have some assemblies that are set as plugin
dependencies. The plugin creates platform-appropriate artifact requests. They
are resolved just fine, then the plugin unpacks them and uses them to enact
some native build methods.
The problem is, when one of
Hey,
thanks a lot! That solved my problems!
Mit freundlichen Grüßen / Best regards
Jan Engler
Central Research Development
SICK AG
Erwin-Sick-Str. 1
79183 Waldkirch, Germany
Phone +49 7681 202-3214
mailto:jan.eng...@sick.de
http://www.sick.com
Von:Thomas Broyer t.bro...@gmail.com
Think of it this way
what do you want to do with the URL?
the url will be used as a SOURCE REPOSITORY for your compiler to extract
its artifacts
the url will be used as one of PLUGIN REPOSITORYs where you will download
your plugins
the url will be used as the URL as a PRIVATE LOCAL REPOSITORY
Hi all,
some colleagues and me are wondering if it is intentional that mvn -amd
does not build submodules which depend on a POM via means of a POM
import in the dependencyManagement section, like so:
dependencyManagement
dependencies
dependency
groupIdamd-test/groupId
Smells like a bug, I'd be interested in other's thoughts, but absence
further input to the contrary, please one a jira
On Monday, 18 March 2013, Ansgar Konermann wrote:
Hi all,
some colleagues and me are wondering if it is intentional that mvn -amd
does not build submodules which depend on a
The problem is, when one of these is a snapshot, the plugin doesn't
bother to check with the remote repository for an update snapshot. If it
sees it in the local repository, it simply goes about its business. Is this
an acceptable method for pulling in platform-specific native packages? If
Interesting. I haven't watched the network traffic yet, but I have checked the
metadata that is cached on the local repository for the artifact[s] in question
and they are not up to date based on the latest timestamp I know to exist on
the remote snapshot repository.
I haven't tried your
Interesting. I haven't watched the network traffic yet, but I have checked the
metadata that is cached on the local repository for the artifact[s] in
question
and they are not up to date based on the latest timestamp I know to exist on
the remote snapshot repository.
I meant to ask, what
Sure! It is Sonatype Nexus.
Patrick
On Mar 18, 2013, at 3:59 PM, Wayne Fay wayne...@gmail.com wrote:
Interesting. I haven't watched the network traffic yet, but I have checked
the
metadata that is cached on the local repository for the artifact[s] in
question
and they are not up to date
Sure! It is Sonatype Nexus.
Can you (easily) construct a test case where you push a snapshot of
something in using just the GAV (no C) and then pull it back it with
your plugin code, then rinse and repeat a few times to confirm it
either works or fails *without* any classifiers?
Then you should
Am 18.03.2013 12:45, schrieb Stephen Connolly:
I would not base your opinion on this one thread.
Joachim got off on the wrong foot by mistaking us trying to guide him
towards a path (where he won't fight maven all the way) for us being
evangelical and spouting religious dogma...
Just for the
On 18 March 2013 23:04, Brian Fox bri...@infinity.nu wrote:
Barrie, the stats for all maven artifacts are available to maven
committers by logging in to the https://repository.apache.org instance
and clicking on Central Stats
Sweet,
Thanks Brian.
Looks like I can't get the overviews I was
On 18 March 2013 21:48, Joachim Durchholz j...@durchholz.org wrote:
Am 18.03.2013 12:45, schrieb Stephen Connolly:
I would not base your opinion on this one thread.
Joachim got off on the wrong foot by mistaking us trying to guide him
towards a path (where he won't fight maven all the way)
Hi Wayne,
I got them to force to update to the latest remote snapshot using mvn -U …,
which I assume is the maven way?
My next questions is: inside the plugin code, how can it know for a given
artifact that it has been updated from remote since the last time the plugin
ran? It seems like the
I got them to force to update to the latest remote snapshot using
mvn -U …, which I assume is the maven way?
Well, the first thing I would check knowing that -U does the update is
the configuration of your repo in your settings.xml. I bet you want an
update policy more like always and it is set
Yeah, I don't know. It makes more sense now.
~K
On 3/18/13, Thomas Broyer t.bro...@gmail.com wrote:
On Mon, Mar 18, 2013 at 6:56 AM, Kevin Krumwiede kjk...@gmail.com wrote:
If the -sources jar is only intended as a reference, then I want to
exclude the generated sources and resources.
Why
30 matches
Mail list logo
