On Mon, Sep 4, 2017 at 2:23 AM, Anders Hammar wrote:
> On Mon, Sep 4, 2017 at 11:09 AM, Thomas Broyer wrote:
>
>> AFAIK, as soon as you use a in a dependency, the transitive
>> dependencies from its POM aren't used (actually, Maven might even not
>> download the POM at all in this case); so you
You have excluded it from the checkstyle plugin, but it's the Java
compiler which is discontented. You need to configure the compiler
plugin, as well.
On Sat, Aug 26, 2017 at 12:03 PM, Seth Goldstein wrote:
> I would have expected that too, however:
>
>
> org.apache.maven.plugins
>
On Fri, Jul 21, 2017 at 2:24 PM, Robert Scholte wrote:
> Hi,
>
> just wondering, are both plugins part of the effective pom?
> When using a plugin prefix like "rat", Maven should first go over all
> plugins and verify if the prefix matches.
> Ensuring that org.apache.rat is above org.codehaus.mojo
AFAIK, That can't be in pom, only settings, and there are many people
who would have to deal with this. Is the problem just that
org.codehaus.mojo is set up in the superpom as a popular destination?
On Fri, Jul 21, 2017 at 12:10 PM, John Patrick wrote:
> Does this help?
> https://maven.apache.or
Maven is 100% Java. If you have a working JDK, you can expect any
binary Maven distro to unpack and then be usable to build other
versions. if you don't have a working JDK, you can't use Maven.
On Fri, May 19, 2017 at 4:35 AM, Ray Sheppard wrote:
> Hello,
> I have tried to find the proper dire
On Mon, Apr 10, 2017 at 8:18 AM, Magnanao, Hector
wrote:
> I'm still a little confused about the answers I'm getting. So, if build A is
> being updated with a new build number(even for a snapshot), and build B has
> it as a dependency in it's pom.file, how does the pom file in Build B need to
On Sun, Mar 5, 2017 at 1:35 PM, Martin Gainty wrote:
> can you suggest a developer list that is responsible for maintaining eclipse
> 2.0?
You are joking, right? Maintain? It's ancient and obsolete. It might
be archived somewhere.
>
>
> vielen danke her eckenfels
>
> Martin
> __
The maven javadoc plugin source tree has no IT's for the aggregate-jar
goal. When I try it in a seemingly obvious way, it fails by feeding
the javadoc tool no java files to process.
Can someone point to a working example?
-
To un
I just tried to configure some offline links in pluginManagement. I
find that this doesn't not seem to be possible, since the pathnames
are interpreted relative to each module. Has anyone else come up with
a solution to this?
-
To
On Sun, Jan 15, 2017 at 3:01 AM, Karl Heinz Marbaise wrote:
> Hi,
>
> On 13/01/17 16:37, Benson Margulies wrote:
>>
>> On Thu, Jan 12, 2017 at 11:42 PM, Florian Schätz
>> wrote:
>>>
>>> Am Donnerstag, den 12.01.2017, 14:22 -0800 schrieb Benson Margu
On Thu, Jan 12, 2017 at 11:42 PM, Florian Schätz wrote:
> Am Donnerstag, den 12.01.2017, 14:22 -0800 schrieb Benson Margulies:
>
>> I agree with them that this is counter-intuitive. The whole point of
>> -beta-1 is to introduce new, incompatible, stuff. The whole point of
&
/www.theoryinpractice.net
>> http://www.chaliceofblood.net
>> http://plus.google.com/+MarkDerricutt
>> http://twitter.com/talios
>> http://facebook.com/mderricutt
>>
>> On 13 Jan 2017, at 11:22, Benson Margulies wrote:
>>
>> > I did not know ho
Coworkers of mine just got bit, badly, by the following:
a range like:
[1.0.0,2.0.0)
INCLUDES
2.0.0-beta-1.
I agree with them that this is counter-intuitive. The whole point of
-beta-1 is to introduce new, incompatible, stuff. The whole point of
that range is to exclude it.
I did not know
Svante,
I bet that problem isn't 'unchangeable', but rather the license.
Anyway, it's easy to do what you want.
Read http://central.sonatype.org/pages/ossrh-guide.html.
You will probably want to put the schema into a zip or tar file, though you
can leave it 'naked'. You set up a github.com repo
An alternative, which I never fully explored, is the CI/CD approach.
Don't use the release plugin. Use -D, or an extension, to set a
unique, non-snapshot, version for each build, and then use version
ranges for the dependencies. I built an experimental extension at my
last job to automatically set
My experience is precisely the opposite of yours. The most common
practice is for the parent to be the aggregator; it's hard to get the
site plugin, for example, to work right with your preferred structure
where they are different.
I have built many projects with the the one-parent structure, and
In spite of the 'warning', this fails the build. Maven 3.3.9.
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules...
[INFO] Installing Nexus Staging features:
[INFO] ... total of 1 executions of maven-deploy-plugin replaced with
nexus-staging-maven-plugin
[INFO]
[INFO
Our experience is that the not-central repos aren't reliable over the
medium term. So, if we can't get it to go to central, we copy it into
our own copy of Nexus. This is, of course, not a helpful strategy for
anything that has to be maintained 'out in the open'.
On Wed, Oct 19, 2016 at 11:16 AM,
ectory.
>
> On Friday, October 14, 2016, jieryn wrote:
>
>> And the dir mismatch in your example is just because of multiple runs?
>>
>> On Thu, Oct 13, 2016 at 8:50 PM, Benson Margulies > > wrote:
>> > ➜ tests git:(master) ls -l
>> > /Users/benson/x/rosa
➜ tests git:(master) ls -l
/Users/benson/x/rosapi1.5/itests/tests/target/pax/6c7a5d80-3080-482f-abb4-394d9a782ef2/data
total 24
-rw-r--r-- 1 benson staff 5 Oct 13 20:47 port
-rw-r--r-- 1 benson staff 7 Oct 13 20:47 rosette-usage.yaml
-rw-r--r-- 1 benson staff 7 Oct 13 20:47 rosette-usage.y
So, here's a specific puzzle. I want to enable multiple branches in
the Jenkins job and concurrent builds. How do I avoid two jobs trying
to write the same local repo at the same time?
-
To unsubscribe, e-mail: users-unsubscr...@m
to do
>>
>> pipeline {
>> agent label:'linux'
>> stages {
>> stage('Build') {
>> // the syntax to specify the Maven tool version is still in progress
>> steps {
>> mvn 'clean verify'
>>
We've about had it with bamboo, and are dusting off our old Jenkins instance.
I recall some messages here about things _not_ to do with Jenkins and
Maven. Do we avoid the 'maven build type' altogether and just run
Maven from the shell, or is my memory faulty? Anything else.
--
Now I get the same thing you do. I better see what's broken in my builds.
On Mon, Oct 10, 2016 at 10:00 AM, Benson Margulies
wrote:
> That's odd. Let me run my test again.
>
>
> On Mon, Oct 10, 2016 at 8:44 AM, Robert Patrick
> wrote:
>> I can confirm that i
in the MANIFEST.MF it says:
>
> Manifest-Version: 1.0
> Built-By: maik
> demo: bad
> Created-By: Apache Maven 3.3.9
> Build-Jdk: 1.8.0_66
>
> So, as I said before, during the execution the property gets set and the
> pre-initialized value is used afterwards.
>
> B
().debug("define property " + name + " = \"" + value + "\"");
}
project.getProperties().put(name, value);
}
On Tue, Oct 4, 2016 at 4:03 PM, Benson Margulies wrote:
> On Tue, Oct 4, 2016 at 5:35 AM, M. Richey wrote:
>> Thanks Benson to point tha
le of a plugin where this is working? I would like to see how they are
> doing it in their code.
I'd better do a test to ensure that they are working as well as I
think they are and then get back to you.
>
> Kind regards,
>
> Maik
>
>
>
>> Gesendet: Sonntag
On Fri, Sep 30, 2016 at 1:50 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> On 30/09/16 15:20, mric...@gmx.de wrote:
>>
>> Hi all,
>>
>> we discovered a problem with properties defined in a pom.xml.
>>
>> Properties could be defined in a pom.xml like:
>>
>>
>> default
>>
>>
>> In a maven plugin we fet
I want checksum:fail for all repos, all the time, without having to
configure it one-at-a-time in settings.xml. Can I have it?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h..
On Tue, Sep 6, 2016 at 7:12 PM, Mark Derricutt wrote:
> On 7 Sep 2016, at 4:16, Benson Margulies wrote:
>
>> In fact, I think I've seen it work. However, today, with Maven 3.3.9,
>> it seems to be having no effect with the declaration below. Can anyone
>> sugges
The doc describes:
*
*
is supposed to work to exclude all transitive dependencies.
In fact, I think I've seen it work. However, today, with Maven 3.3.9,
it seems to be having no effect with the declaration below.
https://github.com/benson-basis/auto-version-example
On Mon, Sep 5, 2016 at 2:09 PM, Karl Heinz Marbaise wrote:
> Hi Benson,
>
> On 05/09/16 16:25, Benson Margulies wrote:
>>
>> I just discovered by experiment that that flatten-maven-plugin helps here.
>>
>
> wo
I just discovered by experiment that that flatten-maven-plugin helps here.
On Thu, Sep 1, 2016 at 1:35 PM, Dan Tran wrote:
> I wonder if Karl's solution facing the same issue
> http://blog.soebes.de/blog/2016/08/08/maven-how-to-create-a-release/
>
> On Thu, Sep 1, 2016 a
Using Maven 3.3.9,
https://github.com/basis-technology-corp/auto-version-maven-extension
is not as useful as I had hoped. The extension sets a property for use
in a element, but 'mvn deploy' deploys the POM as-is, not
after the version is calculated.
Has anyone a suggestion for how to add to this
ould like to check for
> specific line endings.
> So what I'm seeking for is a special option in the maven checkstyle plugin to
> check files
> outside of the normal maven scope (sources, resources).
>
>
>> Gesendet: Mittwoch, 17. August 2016 um 15:21 Uhr
>> Von:
The checkstyle plugin runs http://checkstyle.sourceforge.net/. Which
has a particular feature set, which does not include checking Maven
poms. There are a number of checks in the enforcer plugin which, in
effect, check that the POM meets particular conditions. I don't know
of any way to scan arbitr
We're considering a situation where we want to push artifacts to S3
following the repository pathname convention, but not bother to write
the metadata. In the current state of the universe, what will happen
when something goes to read?
--
I've proved that this is another one of the new bugs in 19/19.1 that
isn't in 18, and I've reported on those in detail before, so I've lost
interest.
On Mon, Jul 11, 2016 at 8:02 AM, Martin Gainty wrote:
> can you attach surefire.log from mvn test e.g.
> mvn -X -e test | tee surefire.log
>
> ?
>
Same failure with 2.19.1. No parallelism configured.
org.apache.maven.plugins
maven-surefire-plugin
2.19.1
-Xmx8G -XX:+UseConcMarkSweepGC
-Djava.io.tmpdir=${project.build.directory}
My build stops with this message just after printing the surefire
summary for the module in question, so none of my test cases called
'exit'. There are no hotspot dumps.
What's the diagnostic process?
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.19:test
(default
It has to be set up as a 'reporting' plugin. I recommend looking at
examples of other such plugins, such as
https://maven.apache.org/plugins/maven-project-info-reports-plugin/
On Sat, Jun 25, 2016 at 4:44 PM, Philipp Kraus
wrote:
> Hello,
>
> I try to build my first Maven site plugin.
> I have de
ways a
great idea. But if you add
subdir/pom.xml
to the m-r-p configuration, it works. I don't have a working example
in a useful place, but there are IT's for it in the m-r-p.
>
> Thanks
>
> -Dan
>
> On Sun, Jun 19, 2016 at 4:14 AM, Benson Margulies
> wrote:
>
You don't put it in the URL.
subdir/pom.xml
On Fri, Jun 17, 2016 at 10:21 PM, Dan Tran wrote:
> Hi
>
> I would like to host multiple multi-module maven projects, each project has
> its own top level folder
> under same GIT repository
>
> is it possible to release each project using maven relea
What do you mean by 'manage package dependencies'? By 'package' do you
mean 'java package' (e.g. com.foo.bar), or do you mean an artifact in
the dependency graph?
Maven is open source. If you want to learn how it works, you need to
read the code.
If you want to learn how to use it, the sonatype o
resolved poms. If
not, I guess, not.
>
> Thanks
>
> -D
>
> On Thu, Apr 21, 2016 at 6:40 PM, Benson Margulies
> wrote:
>
>> On Thu, Apr 21, 2016 at 2:52 PM, Dan Tran wrote:
>> > Hi Benson
>> >
>> > Sounds promissing
>> >
>> &
nstall/deploy time?
if you run mvn deploy, your artifacts will be deployed.
>
> Thanks
>
> -Dan
>
> On Thu, Apr 21, 2016 at 4:00 AM, Benson Margulies
> wrote:
>
>> https://github.com/basis-technology-corp/auto-version-maven-extension
>>
>> On Sat, Apr 16, 2
https://github.com/basis-technology-corp/auto-version-maven-extension
On Sat, Apr 16, 2016 at 2:23 PM, Jeff Jensen
wrote:
>>
>> Jason van Zyl also mentioned he was working on CD solution for Maven last
>> year, not sure what the progress on this front.
>
>
> Yes, I've been curious about the progr
rev}
>> is on the "moan and wail" list
>>
>> On Wednesday 9 March 2016, Benson Margulies > > wrote:
>>
>>> Almost really working. The only gripe is that it is still warning me
>>> that I have an expression in , even when I use 'rev'
l,
line 7, column 14
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer
support building such malformed projects.
[WARNING]
On Wed, Mar 9, 2016 at 5:14 PM, Ben
Of course, as soon as I hit Send I found out what I screwed up.
On Wed, Mar 9, 2016 at 5:12 PM, Benson Margulies wrote:
> I tried this and it didn't work, even a little.
>
> See https://github.com/benson-basis/auto-version-maven-extension.
>
> My extension is never called, w
n Wed, Mar 9, 2016 at 3:24 PM, Benson Margulies wrote:
> On Wed, Mar 9, 2016 at 3:20 PM, Stephen Connolly
> wrote:
>> On Wednesday, 9 March 2016, Benson Margulies wrote:
>>
>>> On Wed, Mar 9, 2016 at 8:51 AM, Tamás Cservenák >> > wrote:
>>> > I
On Wed, Mar 9, 2016 at 3:20 PM, Stephen Connolly
wrote:
> On Wednesday, 9 March 2016, Benson Margulies wrote:
>
>> On Wed, Mar 9, 2016 at 8:51 AM, Tamás Cservenák > > wrote:
>> > I assume it should be this (instead of spy):
>> > http://maven.apache.org/exampl
lue... that is a different question we should ask of the person
>> who implemented this functionality
>>
>> On 9 March 2016 at 13:40, Benson Margulies wrote:
>>
>> > On Tue, Mar 8, 2016 at 2:28 PM, Stephen Connolly
>> > wrote:
>> > &g
On Tue, Mar 8, 2016 at 2:28 PM, Stephen Connolly
wrote:
> In the .mvn folder put an extension that contributes the ${rev} property
> based on whatever you seem safe
Stephen, can you please offer some details? Just what sort of
extension? An event spy that sees session start? Something else? Does
Jason, ping?
On Mon, Jan 25, 2016 at 7:36 AM, Benson Margulies wrote:
> I'm in. How non-public do you need it to be? On github quietly, or
> passed along through some other channel? Either way is fine with me.
>
>
> On Thu, Jan 21, 2016 at 9:17 PM, Jason van Zyl wrote:
>
u like with it.
>
>> On Jan 21, 2016, at 11:47 AM, Benson Margulies wrote:
>>
>> On Thu, Jan 21, 2016 at 2:42 PM, Karl Heinz Marbaise
>> wrote:
>>> Hi Benson,
>>>
>>> you know that you can define the following properties since Maven 3.2.1[1
Marbaise
>
> [1]: http://maven.apache.org/docs/3.2.1/release-notes.html
>
> On 1/20/16 1:11 PM, Benson Margulies wrote:
>>
>> Some time ago, I recall some email about dynamic versioning; the idea
>> being that all the elements in all the POMs of the project
>>
Some time ago, I recall some email about dynamic versioning; the idea
being that all the elements in all the POMs of the project
would look like ${version}, and a jar dropped into
the maven extensions directory would provide a component that would
generate the version, perhaps from a git hash or s
What evidence do you have that wildcard exclusions work at all? I'd
appreciate a pointer.
On Fri, Jan 15, 2016 at 9:47 PM, Jamie Johnson wrote:
> I was trying to look at my applications dependency tree and noticed that it
> appears that wildcard expressions in exclusions do not get reflected in t
I was wrong, as I noted elsewhere. 2.18 good, 2.19.x bad.
On Thu, Jan 14, 2016 at 7:57 PM, Benson Margulies wrote:
> 2.19.1 is just as broken in these cases.
>
> On Tue, Jan 12, 2016 at 3:57 PM, Andreas Gudian
> wrote:
>> You might wanna try 2.19.1, where Tibor fixed
I have a rather complex project using pax-exam that works fine with
2.18 and not with 2.19 or 2.19.1, contrary to some confused email I
sent the other day. Setting forkCount to 0 makes the immediate problem
go away, but messes up other things for me because of the different
working directory when r
2.19.1 is just as broken in these cases.
On Tue, Jan 12, 2016 at 3:57 PM, Andreas Gudian
wrote:
> You might wanna try 2.19.1, where Tibor fixed a couple of issues regarding
> the fork-communication that crept in to 2.19.
>
> 2016-01-12 15:13 GMT+01:00 Benson Margulies :
>
>>
:09 AM, Benson Margulies wrote:
> I'm suddenly suffering from the following, is there any diagnostic
> procedure recommended?
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-failsafe-plugin:2.19:integration-test
> (integration-tests) on project rosapi-
I'm suddenly suffering from the following, is there any diagnostic
procedure recommended?
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-failsafe-plugin:2.19:integration-test
(integration-tests) on project rosapi-itests-tests: Execution
integration-tests of goal
org.apache.maven.plu
te:
>
>> Most likely it is in one of the spring poms. Can't you search for that id
>> in all poms in your local Maven repo?
>>
>> /Anders (mobile)
>> On Dec 11, 2015 15:38, "Benson Margulies" wrote:
>>
>>> I can't build Apache CXF whe
I can't build Apache CXF when my normal Nexus mirror is in place; it
fails to find:
org.springframework:org.springframework.context:2.5.6.SEC01
I can if I turn off my mirrors. So, I'm trying to determine what repo
I need to add to my Nexus or exclude from my mirrors.
Mirrorless, I see
➜ 2.5.6.S
None of this is relevant to the simple build process of incorporating
a feature in a karaf assembly.
Adding 'install' to the preparationGoals of the release plugin is the
workaround.
On Wed, Oct 21, 2015 at 8:41 PM, Martin Gainty wrote:
>
>
>> Date: Wed, 21 Oct 2015 13:56:39 -0400
>> Subject: R
I've hit a problem with Maven 3.2.5 and the karaf-maven-plugin.
One module builds a Karaf feature with the karaf maven plugin; this produces:
${project.groupId}
rosapi-features
${project.version}
features
xml
runtime
> using profiles means that you have to execute the build itself to validate,
> while using the archetype, you test the structure and content of the
> created project, which I find easier.
>
>
>
> Patrick Sansoucy
> In theory, there is no difference between theory and practice,
Once you've run an archetype, you have a new project. And you're stuck
with it, in the sense that you have to keep it maintained.
An important question is this: what artifacts do you want to make as
part of a release? If you want a portfolio of artifacts, each for one
of your scenarios, then profi
The Apache Maven team is pleased to announce the release of the Apache
Maven Plugins parent POM, version 28.
This POM is the common parent of all of the plugins maintained by the
Apache Maven PMC, and, as such, is of limited use to developers
outside of the Maven project. See the svn history of
ht
Laird,
I really can't help you with this, I was 99% just the release manager of
this thing. I recommend, however, reading the source of the
maven-dependency-plugin, which uses the new API.
On Mon, Oct 12, 2015 at 3:01 PM, Laird Nelson wrote:
> On Sat, Oct 10, 2015 at 12:04 PM
The Maven team is pleased to announce the release of the Apache Maven
Dependency Tree, version 3.0
A tree-based API for resolution of Maven project dependencies
http://maven.apache.org/shared/maven-dependency-tree/
You should specify the version in your project's dependency configuration:
or
The Apache Maven team is pleased to announce the release of the Apache
Maven Assembly Plugin, version 2.6
This plugin builds directories and archives of files, usually for releases.
http://maven.apache.org/plugins/maven-assembly-plugin/
You should specify the version in your project's plugin con
t; Hi,
>
> On 10/2/15 11:06 PM, Benson Margulies wrote:
>>
>> I've just tried version ranges for the first time, and I hit a pothole.
>>
>> Step 1: set version in dependency to: 7.14.0.c52.2. Run a build.
>>
>> Step 2: change version in pom to [7.13.5
I've just tried version ranges for the first time, and I hit a pothole.
Step 1: set version in dependency to: 7.14.0.c52.2. Run a build.
Step 2: change version in pom to [7.13.500.c52.2,7.13.600.c52.2).
Now, mvn dependency:whatever shows the correct resolution, but an
actual build stubbornly us
I've got a utility module with modello in it. I want to pull the xdoc
from that into the site doc of a plugin that uses it. Do I need to
'attach' it and then use the dependency plugin to grab it? I don't see
a way in the site plugin to add additional site content directories,
only to change the loc
This is a bug in the maven-bundle-plugin, as it turns out.
On Tue, Aug 25, 2015 at 1:46 PM, Benson Margulies wrote:
> One of our builds has developed a stutter.
>
> These log messages (and the details and work that go with them) are
> repeating several times. I can't find
One of our builds has developed a stutter.
These log messages (and the details and work that go with them) are
repeating several times. I can't find any evidence of a forked
lifecycle, but maybe I've forgotten how to look.
[DEBUG] --
On Mon, Aug 10, 2015 at 11:04 AM, Alex Ditu wrote:
> I know how to solve my problem (by changing the project configuration).
>
> My question is: why mvn -f otherPomName.xml deploy doesen't work? And I
> said above how it fails.
It does not _fail_. It does precisely what it is designed to do.
mvn
Formally, a project has can only produce one POM artifact. So, you can
do whatever you want with -f, but when it comes to install or deploy,
you are pushing the one-and-only pom (selected from the file system
with -f), and it gets the immutable, conventional, name of the pom
artifact in the reposit
false
On Sun, Aug 2, 2015 at 4:40 PM, Kevin Burton wrote:
> The Maven jdeb plugin (for building debian packages) recommends you set it
> up like:
>
>
>
> package
>
> jdeb
>
>
> … but this means that if I do an
>
> mvn install
>
> tha
Look for the modern nar plugin on github.
On Fri, Jul 31, 2015 at 12:59 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> On 7/31/15 6:51 PM, Dušan Rychnovský wrote:
>>
>> Hi,
>>
>> I'm creating a JNI wrapper on top of a C++ library. I'd like to have a
>> "one-click" Maven build for the whole application.
Yes, it's to do with the forked execution. I've made a test case and
created https://issues.apache.org/jira/browse/MRELEASE-915.
I haven't tried the yet, I will in a moment and
annotate the JIRA.
On Sun, Jul 12, 2015 at 1:08 PM, Benson Margulies wrote:
> On Sat, Jul 1
gt; is leaking.
> Could you try to switch to the ForkedMavenExecutor?
> forked-path
Where do I put that? release plugin config?
>
> thanks,
> Robert
>
> Op Fri, 10 Jul 2015 03:04:55 +0200 schreef Benson Margulies
> :
>
>> Ever since we bumped to 2.15 of the plugin,
Ever since we bumped to 2.15 of the plugin, we've been hitting a
problem. I don't have a concise repro, so I'm not opening a JIRA yet,
but I thought I'd inquire for other people's experience.
We use some source generators, and none of them generate source that
is acceptable to our checkstyle rules
> K
> 9. jul. 2015 3.16 a.m. skrev "Benson Margulies" :
>
>> Port 5005 is NOT in use, but I get the following. What's up?
>>
>> SUREFIRE-859: FATAL ERROR in native method: JDWP No transports
>> initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Port 5005 is NOT in use, but I get the following. What's up?
SUREFIRE-859: FATAL ERROR in native method: JDWP No transports
initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
SUREFIRE-859: ERROR: JDWP Transport dt_socket failed t
Once formatted, this is very interesting.
It doesn't quite solve the problem I started with, which that the
plain POM version of this project is not OSGi friendly, even before we
get to -SNAPSHOT.
But it's way cooler than just sticking .SNAPSHOT on the end, so I'm
going to combine it with my othe
We don't seem to have a mojo user mailing list post-codehaus, do we?
I'm trying to use the regexPropertySettings goal to map from Maven
version to OSGi version, since I need the OSGi version in more places
than just the manifest.
I can't figure out how to account for -SNAPSHOT well. It does not w
Put a proxy in front of Nexus.
On Tue, Jun 9, 2015 at 1:51 AM, Thomas Klöber
wrote:
> Hi Ron,
>
> might have not explained it right: jarfile3.jar gets turned into
> jarfile3-x.x.x.jar due to the version number i have to supply when creating
> the artefact in nexus.
>
> I agree it would be easie
First, treating build as a separate discipline from code is, in my
experience, a recipe for trouble. The poms or build.xml or whatever
files are just as much part of the source code as the java. Someone
may own Jenkins or whatever, but the devs should own the building of
the code they write.
Secon
I cannot imagine how anyone could expect a command-line tool for software
developers to be relevant to 508. We've never considered the question for
Maven and I don't think that we ever will. You might look into how people
treat, for example, 'make' as an model.
On Thu, Apr 23, 2015 at 9:34 AM,
The Apache Maven team is pleased to announce the release of Apache
Maven Archetype 2.3.
Archetype is a tool for setting up new Maven projects.
This is the last release intended to provide support for Maven 2.2.x.
Release notes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095&ve
I don't understand your question at all. In Maven, you can just use the
build-helper-maven-plugin to attach any file to the project, causing it to
upload. So, you can certainly use antrun to run the ant build, and the
helper to attach the result as an artifact.
On Sun, Mar 1, 2015 at 4:18 PM, Bruc
Please ignore this, I see what I screwed up.
On Fri, Jan 16, 2015 at 8:16 AM, Benson Margulies wrote:
> I'm a bit puzzled.
>
> I can deploy a staged release for org.apache.nifi, but I can't push a
> snapshot, I get permission denied.
>
> Error:
>
>
>
I'm a bit puzzled.
I can deploy a staged release for org.apache.nifi, but I can't push a
snapshot, I get permission denied.
Error:
https://repository.apache.org/content/repositories/snapshots/org/apache/nar-maven-plugin/0.0.2-test-incubating-SNAPSHOT/nar-maven-plugin-0.0.2-test-incubating-2015
Failsafe isn't what I'd use for that, but rather the invoker.
On Tue, Jan 6, 2015 at 4:49 PM, SDOCA SDOCA wrote:
> Hi,
>
> Can somebody provide a link to an sample project that uses the Failsafe
> plugin to do integration tests that include deploying as per the lifecycle
> phase integration-te
I think that what you actually want is two executions of surefire (or
one of surefire and one of failsafe) with different test name
patterns.
On Thu, Jan 1, 2015 at 2:40 PM, Ole Ersoy wrote:
> Hi,
>
> I'm attempting to separate my integration and unit tests using profiles and
> the maven build he
On Thu, Jan 1, 2015 at 5:29 PM, Ole Ersoy wrote:
> Had one more question. In the documentation I have read the integration
> test directory is usually added in the generate-test-sources phase. So all
> tests are visible during the `test` phase, although they would be excluded
> by default if the
1 - 100 of 762 matches
Mail list logo
