Hi there,
I just added consumer-maven-plugin to MOJO sandbox:
https://svn.codehaus.org/mojo/trunk/sandbox/consumer-maven-plugin
To get directly to the MOJO code use this link:
https://svn.codehaus.org/mojo/trunk/sandbox/consumer-maven-plugin/src/main/java/org/codehaus/mojo/consumer/ConsumerMojo.
Am 26.02.2014 20:15, schrieb Vincent Latombe:
Hi Jörg,
Hi Vincent,
thanks for writing this; I think it solves in a nice way the
"consumer" pom issue.
thanks for your feedback.
Some initial remarks :
- instead of consumerPomFile, I would use the generic outputDirectory
to specify the dire
Am 26.02.2014 21:08, schrieb Robert Scholte:
Hi Jörg,
Hi Robert,
I did some small modifications.
I had a quick look. Awesome. Some time passed since I wrote my last MOJO
and this code was a little old-fashioned. Nicer with annotations...
Thanks.
Most important: introduce the mock repositor
Hi there,
I need help from a real maven expert - see below...
Am 26.02.2014 23:51, schrieb Jörg Hohwiller:
Am 26.02.2014 21:08, schrieb Robert Scholte:
[...]
The resolve-properties now exposes a small issue: the property is not
resolved.
I hope you can fix that.
Sure. That is coming from the
ts to my
problem, I can try instantiating StringSearchInterpolator as I assume
this is the core logic used to do the interpolation. Any hints would
help for my enlightenment...
Robert
Regards
Jörg
Op Thu, 27 Feb 2014 00:51:43 +0100 schreef Jörg Hohwiller
:
Hi there,
I need help from
here are many forums about this error message, but I could not find
anything really helpful in my case.
Regards
Jörg
Am 27.02.2014 00:51, schrieb Jörg Hohwiller:
Hi there,
I need help from a real maven expert - see below...
Am 26.02.2014 23:51, schrieb Jörg Hohwiller:
Am 26.02.2014 21:08, sc
core Maven coder for hints to my
problem, I can try instantiating StringSearchInterpolator as I assume
this is the core logic used to do the interpolation. Any hints would
help for my enlightenment...
Robert
Regards
Jörg
Op Thu, 27 Feb 2014 00:51:43 +0100 schreef Jörg Hohwiller
:
Hi ther
Hi Stephen,
Am 28.02.2014 23:59, schrieb Stephen Connolly:
On 28 February 2014 22:48, Jörg Hohwiller <mailto:jo...@j-hohwiller.de>> wrote:
Am 27.02.2014 22:12, schrieb Robert Scholte:
Hi Jörg,
Hi Robert,
I think I found the solution without the Int
u can't release from the sandbox, you
need to call for a vote first to get it out of the sandbox.
Mojo doesn't use the 0.9.0, but 1.0-alphas or -betas, see
http://mojo.codehaus.org/development/process.html
Robert
Op Fri, 28 Feb 2014 23:48:36 +0100 schreef Jörg Hohwiller
:
Am
re
complicated.
How shall we proceed?
Regards
Jörg
Am 03.03.2014 12:33, schrieb Jörg Hohwiller:
Hi Robert,
thanks for all your hints and ideas. I very much appreciate your
support :)
So I will dive further this week...
Best Regards
Jörg
Am 01.03.2014 21:16, schrieb Robert Scholte:
you
need to call for a vote first to get it out of the sandbox.
Mojo doesn't use the 0.9.0, but 1.0-alphas or -betas, see
http://mojo.codehaus.org/development/process.html
Robert
Op Fri, 28 Feb 2014 23:48:36 +0100 schreef Jörg Hohwiller
:
Am 27.02.2014 22:12, schrieb Robert Scholte:
lock-down in 4.0.0 modelVersion poms that we will need to apply or
else we
will have to go in search of a different term
On 3 March 2014 11:31, Jörg Hohwiller wrote:
Hi Stephen,
Am 28.02.2014 23:59, schrieb Stephen Connolly:
On 28 February 2014 22:48, Jörg Hohwiller wrote:
Am 27.02.20
Robert
Op Thu, 06 Mar 2014 23:00:35 +0100 schreef Jörg Hohwiller
:
Hi Robert,
I found an "unexpected exception feature" ;)
I have tested consumer on a GWT project and get this exception:
> Caused by: java.lang.IllegalStateException: Duplicate dependency!
Original: net.sf.m
Am 08.03.2014 12:35, schrieb Robert Scholte:
Hi Jörg,
Hi Robert,
After rescanning the code, I wasn't convinced of embedding/moving the
dependencies from profiles activated by properties of files, because
the result would be different if the original pom.xml was deployed and
Maven would then
d ITs are running.
I will also open a new thread as the topic does not fit anymore.
Robert
Cheers
Jörg
Op Sun, 09 Mar 2014 21:30:10 +0100 schreef Jörg Hohwiller
:
Am 08.03.2014 12:35, schrieb Robert Scholte:
Hi Jörg,
Hi Robert,
After rescanning the code, I wasn't convinced of em
Hi there,
I hope renaming of consumer-maven-plugin to flatten-maven-plugin was
perfectly correct.
We should have another SNAPSHOT version released for testers.
Then I will update the related JIRA issues with that.
I still have to add some documentation for the site...
If there is anything els
cents.
2014-03-09 23:16 GMT+01:00 Jörg Hohwiller :
Hi there,
I hope renaming of consumer-maven-plugin to flatten-maven-plugin was
perfectly correct.
We should have another SNAPSHOT version released for testers.
Then I will update the related JIRA issues with that.
I still have to add some d
a
vote to release.
My 2 cents.
2014-03-09 23:16 GMT+01:00 Jörg Hohwiller :
Hi there,
I hope renaming of consumer-maven-plugin to flatten-maven-plugin was
perfectly correct.
We should have another SNAPSHOT version released for testers.
Then I will update the related JIRA issues with that.
I sti
Hi Robert,
Am 13.03.2014 21:43, schrieb Robert Scholte:
Op Thu, 13 Mar 2014 01:40:23 +0100 schreef Jörg Hohwiller
:
Hi there,
I added site documentation and some other missing infos. Further I fixed
some JavaDoc issues.
For clarification I found the following questions:
* Why do we copy
Hi there,
I'd like to promote the flatten-maven-plugin out of the Sandbox
Flatten Maven Plugin generates a flattened version of your pom.xml and makes
maven to install and deploy this one instead of the original pom.xml.
This offers a workaround for some JIRA issues like:
http://jira.codehaus.o
+1
Am 31.03.2014 18:38, schrieb Simon Brandhof:
Hi,
Julien would like to commit to the sonar plugin. He's a full-time
contributor to SonarQube and he's already aware about the development
process of Mojo projects.
Any objection ?
His xircles account is "henryju".
Thank you very much
Simon
This vote has passed with the following results:
+1: 5 votes - Robert Scholte (rfscholte), Arnaud Héritier (aheritier),
Mirko Friedenhagen (mfriedenhagen), Karl Heinz Marbaise (khmarbaise),
Tony Chemit (tchemit)
0: none
-1: none
I will move the flatten-maven-plugin folder from sandbox to mojo
Hi there,
I have moved flattend-maven-plugin out of sandbox:
* moved folder in svn
* change pom (updated parent)
* removed sandbox skin in site.xml
* moved plugin link in plugins.apt (already with upcoming version that
is not yet released).
For the actual release I would follow
http://mo
the meantime fixes something and redeploys the website, there wll
be a reference to flatten-maven-plugin not yet existing.
Also beware using a JDK5 locally for releasing to prevent any unwanted
usage creeping in (as we didn't set up animal-sniffer IIRC).
Have fun.
Cheers
2014-04-04 0
uld be
aware of the status of the plugin, developers should be motivated
to move it faster to a final version.
>
>regards,
>Robert
>
>Op Mon, 07 Apr 2014 23:22:24 +0200 schreef Jörg Hohwiller <
jo...@j-hohwiller.de <mailto:jo...@j-hohwiller
Hi there,
I am trying to release flatten-maven-plugin and follow the given processes.
However it is simply not working. I made several tries but always get
errors with release:prepare.
All my last tries ended up with this error:
[ERROR] svn: E160013:
'/mojo/!svn/bc/19650/tags/mojo-parent-33/f
as I hoped it to be...
Thanks & regards
Jörg
Am 12.04.2014 22:44, schrieb Robert Scholte:
Hi,
Looks like the pom.xml is missing the scm-section, which is required
for all mojo projects. The value based on inheritence is invalid.
Robert
Op Sat, 12 Apr 2014 22:40:45 +0200 schreef Jörg H
Hi Mathus,
thanks for your response.
Am 22.04.2014 22:28, schrieb Baptiste Mathus:
Did you succeed with a simple 'mvn deploy' of a snapshot as I said
previously? That would prevent you from trying to release by first
getting the auth right with a simpler process than a release one.
Because de
Hi,
Am 23.04.2014 19:34, schrieb Jörg Hohwiller:
Indeed "mvn deploy" fails as well. It does not even ask me for PGP
passphrase. So how does the authentication work.
Obviously I missing something and after double-checking I found it:
http://mojo.codehaus.org/development/pe
Hi again,
I finally made it. As I did not change anything compared to the last
try, I assume that there was a permission problem with my account that
has been fixed by somebody. Thanks...
Cheers
Jörg
Am 23.04.2014 19:47, schrieb Jörg Hohwiller:
Hi,
Am 23.04.2014 19:34, schrieb Jörg
Hi,
I'd like to release version 1.0.0-beta-1 of the flatten-maven-plugin
Flatten Maven Plugin generates a flattened version of your pom.xml
and makes maven to install and deploy this one instead of the original
pom.xml.
All planned features have been implemented, there are currently no outstand
Hi Karl-Heinz
I was too late for +1
However, thanks for the fixes and improvements. I once issued MEXEC-104
that is now fixed.
Thanks
Jörg
Am 22.04.2014 21:24, schrieb Karl Heinz Marbaise:
This vote has passed with the following result:
lazy census.
+1 : None
0: none
-1: none
I will pro
+1 from me to avoid boring empty consensus ;)
Jörg
Am 26.04.2014 00:15, schrieb Jörg Hohwiller:
Hi,
I'd like to release version 1.0.0-beta-1 of the flatten-maven-plugin
Flatten Maven Plugin generates a flattened version of your pom.xml
and makes maven to install and deploy this one in
+1
BTW: about time to go for a beta? Maybe some of the open bugs is still
nasty but I did not face any of them for my usecases...
Thanks & regards
Jörg
Am 27.04.2014 21:55, schrieb Rickard von Essen:
Hi,
I'd like to release version 2.1-alpha-4 of the rpm-maven-plugin
The RPM Maven Plugin
This vote has passed with the following results:
+1: 2 votes - Robert Scholte (rfscholte), Jörg Hohwiller (joerg.hohwiller)
0: none
-1: none
I will process the release.
Cheers
Jörg
smime.p7s
Description: S/MIME Cryptographic Signature
Hi there,
I just wanted to release my first OSS project module with
flatten-maven-plugin.
Now I figured out that OSSHR nexus is preventing the release with this
message:
Invalid POM: /net/sf/m-m-m/mmm-util-core/4.0.0/mmm-util-core-4.0.0.pom:
Project name missing, Project description missing, P
On 01.05.2014 16:19, Karl Heinz Marbaise wrote:
Hi Jörg,
Hi Karl-Heinz,
> Hi there,
I just wanted to release my first OSS project module with
flatten-maven-plugin.
Now I figured out that OSSHR nexus is preventing the release with this
message:
Invalid POM: /net/sf/m-m-m/mmm-util-core/4.0.0/
Hi,
The Mojo team is pleased to announce the release of the flatten-maven-plugin
version 1.0.0-beta-1.
Flatten Maven Plugin generates a flattened version of your pom.xml and makes
maven to install
and deploy this one instead of the original pom.xml.
http://mojo.codehaus.org/flatten-maven-plug
Am 01.05.2014 22:13, schrieb Robert Scholte:
Hi,
Hi Robert,
the current result of a flattened pom contains only the information
required other projects need to be ably to *use* this artifact,
nothing more, nothing less. It's all Aether needs.
So now it seems that some artifact repositories r
Am 01.05.2014 20:47, schrieb Karl Heinz Marbaise:
Hi Jörg,
Hi Karl-Heinz,
>>> I kept some of these informations but removed them after suggestions
from Robert.
When did you suggested this?
I do not want any finger-pointing and I did not suggested this from my
wisdom foreseeing this trouble
Hi Mikro,
are you saying that if flatten-maven-plugin is active in your build
section then site generation is impacted negatively?
Can you confirm that your site.xml problem goes away if you comment out
flatten-maven-plugin?
I have not yet observed this... The only reason if this is really
hap
Hi there,
how could I create a project or at least a project version in JIRA?
IMHO I do not have permissions to do so.
I would like to file an issue for a new feature for
flatten-maven-plugin, that I am maintaining.
On the long run, I would like to create a new project for this MOJO.
Thanks
Am 05.05.2014 22:27, schrieb Robert Scholte:
Hi Jörg,
Hi Robert,
I think we should consider another approach.
Once users can define their own descriptors, you really want to get
rid of these parameters.
For now I would go for:
@Parameter
private String descriptorId;
For now it's null by de
com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Sat, May 3, 2014 at 10:15 PM, Jörg Hohwiller wrote:
Hi Mikro,
are you saying that if flatten-maven-plugin is active in your build section
then site generation is impacted negatively?
Can you co
he bare minimum required by the OSS Nexus. If you
want more freedom to choose your fields, don't use ids, just a
descriptor.
thanks,
Robert
Op Mon, 05 May 2014 23:45:18 +0200 schreef Jörg Hohwiller
:
Am 05.05.2014 22:27, schrieb Robert Scholte:
Hi Jörg,
Hi Robert,
I think we sho
to go for a
release soon since I fixed an important bug...
Regards
Jörg
Am 12.05.2014 22:23, schrieb Jörg Hohwiller:
Hi Robert,
I would try to refactor as suggested. However to get everything clear:
The Mojo would be shipped with predefined descriptor configs that
would be read from the c
Am 24.05.2014 12:03, schrieb Robert Scholte:
Hi,
Hi Robert,
seems like I missed a mail.
no worries...
What I don't understand is why you want to overcomplicate things by
using KeepOrAdd (and what would the value of add be?), KeepIfExist and
remove. I'd prefer to just naming those elements y
Am 24.05.2014 01:26, schrieb Sergei Ivanov:
Hello Jörg,
Hi Sergei,
I have two minor suggestions:
1. Rename flattenDescriptor to pomSections (or pomElements)
2. Start enumerated constants with a lower case letter, e.g. keepIfExists, so
that they are consistent with other mojos' configuration
tead?
Also lists the elements to keep. In the context of
flattening one might initially expect the opposite.
As soon as this is finallized I would love to go for the next release.
Cheers Jörg
[1]
http://blog.sonatype.com/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/
Hi,
Hi Jörg,
Hi Robert,
I very much appreciate your support and contribution.
However, your "in the middle of the discussion" commit caused me some
SVN conflict and merge trouble.
I did my best to resolve but as a consequence removed a part of your
changes (Model vs. FlattenDescriptor).
Howev
Hi,
I'd like to release version 1.0.0-beta-2 of the flatten-maven-plugin
Flatten Maven Plugin generates a flattened version of your pom.xml
and makes maven to install and deploy this one instead of the original
pom.xml.
These issues have been fixed (1 feature, 1 bugfix):
http://jira.codehaus.or
Hi everybody,
the result is:
+1: 1 vote (mfriedenhagen)
0: none
-1: none
sorry for the delay. I was on tour and had trouble to access mail (I
only watched in markmail). Release is out.
Regards
Jörg
smime.p7s
Description: S/MIME Cryptographic Signature
Hi,
The Mojo team is pleased to announce the release of the
flatten-maven-plugin version 1.0.0-beta-2.
Flatten Maven Plugin generates a flattened version of your pom.xml and
makes maven to install
and deploy this one instead of the original pom.xml.
http://mojo.codehaus.org/flatten-maven-pl
Hi Esteban,
(now with reply on list...)
you are right with your guess.
> I am curious as to how well it works with the release plugin,
versions plugin,
> packaging sources, generating sites, eclipse, m2eclipse, other
plugins in general.
For site generation we had a bug that has been fixed in
Hi there,
I am not a groovy expert and need some help.
An IT of flatten-maven-plugin fails with this error:
assert 'no-one' == flattendProject.repositories.repository.id
| | || |
| | || no-one
String
Op Thu, 04 Sep 2014 21:59:54 +0200 schreef Jörg Hohwiller
:
Hi there,
I am not a groovy expert and need some help.
An IT of flatten-maven-plugin fails with this error:
assert 'no-one' == flattendProject.reposi
Hi there,
In order to change the license of the source-code of an open-source
project the official procedure is that all authors that contributed
(reasonable) to the code give their agreement (potentially by signature).
This is especially for larger projects a big procedure.
I personally see
Hi there,
unfortunately there seems to be no other idea and I am lost with this.
As the result of the Mojo is correct and only groovy is nuts here, I
would tend to comment out the assertion so we can go for the next release.
Cheers
Jörg
Am 04.09.2014 22:24, schrieb Jörg Hohwiller:
Hi
Am 16.09.2014 23:48, schrieb Sergei Ivanov:
Have you seen my patch attached to the JIRA?
Sorry, I have been busy and was therefore out of action on MOJO.
Sergei, you saved my day! Thanks for giving me the correct hint to add
".text()".
All obvious now. Awesome.
Thanks
Jörg
--
Sergei Ivan
Hi,
I'd like to release version 1.0.0-beta-3 of the flatten-maven-plugin
Flatten Maven Plugin generates a flattened version of your pom.xml
and makes maven to install and deploy this one instead of the original
pom.xml.
These issues have been fixed:
http://jira.codehaus.org/browse/MOJO-2032
htt
Hi Karl Heinz,
> Site seemed to be not being updated ...acording to the release...
thanks for double checking. According to my logs there was a certificate
error - this JSSE thing and keystore hacking in JVM is painful as I have
tons of JVMs on my machine
Fixed.
Hope this did not disturb
-
[INFO]
[INFO] BUILD FAILURE
[INFO]
I have attached the appropriate log file of the integration test for
further analysis...
On
Jörg
Am 28.09.2014 21:58, schrieb Robert Scholte:
Hi,
FYI: I'm having the same issue as Karl-Heinz: the external-parent IT
fails.
I've checked out
http://svn.codehaus.org/mojo/tags/flatten-maven-plugin-1.0.0-beta-3/
and executed 'mvn verify'.
Robert
Op Sun, 28 Sep 2014
. The one below is M3.2.3+ specific.
thanks,
Robert
Op Tue, 30 Sep 2014 23:46:48 +0200 schreef Jörg Hohwiller
:
Hi Robert,
thanks also for your feedback and testing. So something is wrong.
But I just checked out the tag again and "mvn verify" succeeds - no
error with external-
Hi Robert,
We got this as a feature request via this issue:
http://jira.codehaus.org/browse/MOJO-2041
I see the use-case of the requester and wanted to support this.
Did you properly read and understand his point?
He is actually talking about POM projects but he wants to have variables
resolved
let's wait for the example. I also want to ensure that the behavior
between the real and flattened pom stays the same, because I think
that this will change with the suggested fix.
Robert
Op Sun, 19 Oct 2014 21:45:20 +0200 schreef Jörg Hohwiller
:
Hi Robert,
We got this as a feature r
solution ;)
So let's wait for the example. I also want to ensure that the behavior
between the real and flattened pom stays the same, because I think
that this will change with the suggested fix.
Robert
Op Sun, 19 Oct 2014 21:45:20 +0200 schreef Jörg Hohwiller
:
Hi Robert,
We got this as a
Hi,
I'd like to release version 1.0.0-beta-3 of the flatten-maven-plugin
Flatten Maven Plugin generates a flattened version of your pom.xml
and makes maven to install and deploy this one instead of the original
pom.xml.
These issues have been fixed:
http://jira.codehaus.org/browse/MOJO-2032
htt
Hi,
This vote has passed with lazy consensus. I will promote the release to
central.
Regards
Jörg
Am 28.10.2014 19:20, schrieb Jörg Hohwiller:
Hi,
I'd like to release version 1.0.0-beta-3 of the flatten-maven-plugin
Flatten Maven Plugin generates a flattened version of your pom.xm
Hi,
The Mojo team is pleased to announce the release of the
flatten-maven-plugin version 1.0.0-beta-3.
Flatten Maven Plugin generates a flattened version of your pom.xml and
makes maven to install
and deploy this one instead of the original pom.xml.
http://mojo.codehaus.org/flatten-maven-pl
Hi there,
I would like to take flatten-maven-plugin out of the beta phase and plan
the next release as an official version.
The plugin has proven success in various projects some of them with >
100 modules and more than 4 levels of module depth. Also the combination
with m2e does not cause any
>
> On 11/20/14 10:05 PM, Jörg Hohwiller wrote:
>> Hi there,
>>
>> I would like to take flatten-maven-plugin out of the beta phase and plan
>> the next release as an official version.
>> The plugin has proven success in various projects some of them with >
Hi there,
I would like to open a discussion about the design of flatten-maven-plugin.
Important issue is http://jira.codehaus.org/browse/MOJO-2041
Therefore I already applied the old code back onto trunk and did some
rework.
1. I will remove "build" and "parent" support as this really makes no
se
Hi Robert,
> you can't use attributes unless you do the parsing yourself. I'd still
> love to see ITs showing the usage, it is still not there.
Did you have a look at my BOM IT? Probably you missed it...
https://svn.codehaus.org/mojo/trunk/mojo/flatten-maven-plugin/src/it/projects/bom
For attribu
; some parts of the pattern, because to me it still would look like
>> this change is not required: a jar having a bom as dependency with
>> 'import' scope should still have the same result.
>>
>> thanks,
>> Robert
>>
>> Op Sat, 14 Feb 201
Hi there,
I refactored the flatten-maven-plugin and completed the BOM support.
Everything is now tidied up and flexible. Maybe a little bit of
swiss-army-knife feature in pomElements but this is only for the really
advanced usage and shall not be used in regular cases. So I think we
have the best
Hi there,
(mail was stuck in outbox - sorry for delay)
sounds great. I am a big fan of the github platform.
In that case we should also discuss if we create one repo for each MOJO
instead of having one for all as we currently have in SVN (what actually
sucks).
Then only the core maintainers of eac
Hi there,
I do have permissions yet and PR seems overkill:
joerg.hohwiller - that is me.
Full name: Jörg Hohwiller
Email: jo...@j-hohwiller.de (or hohwi...@users.sourceforge.net)
Github account: https://github.com/hohwille
Thanks
Jörg
Am 08.04.2015 um 10:53 schrieb Baptiste Mathus:
> The f
Hi,
plan sounds great.
+1
do you already have a (rough) roadmap/schedule? When should we stop
working in SVN, wenn will the Git repos be available?
Thanks
Jörg
Am 08.04.2015 um 09:03 schrieb Baptiste Mathus:
>
> Forking the thread to focus around Git tinkering.
>
> FWIW, some of you already n
Hi there,
I guess jira export is not the problem. GH support for automated import
will be more of a challange.
In the worst case we will lose all old issues...
Creating issues via Web-API is possible with some scripting but "faking"
authors and dates will IMHO not work this way...
Regards
Jörg
Hi,
+1 for that as well from my side.
Joining maven dev will be a lot of traffic all together but is makes
perfectly sense...
Regards
Jörg
Am 09.04.2015 um 23:55 schrieb Mirko Friedenhagen:
>
> Hello,
>
> +1 for going with google groups, I do not like Ads and the list search
> is really impor
Hi there,
I guess this will not be the codebase for the final migration as there
was not announcement for a "code freeze".
Just in case you need several runs: For taking a dump of an SVN repo you
do not even need server-side access. Just use svnsync to clone the
entire repo to a full local copy an
Hi,
I'd like to release version 1.0.0-beta-4 of the flatten-maven-plugin
Flatten Maven Plugin generates a flattened version of your pom.xml
and makes maven to install and deploy this one instead of the original
pom.xml.
These issues have been fixed:
http://jira.codehaus.org/browse/MOJO-2041
http
Hi Alexander,
thanks for your input. I created a JIRA issue:
http://jira.codehaus.org/browse/MOJO-2080
Already fixed on trunk.
Unfortunately I process the mails in wrong order and just started a vote
for release beta4 that does not include the fix.
We can either drop the vote or otherwise have t
Hi,
This vote has passed with lazy consensus, I will proceed to promote the
artifact to Maven Central
Right next I will start the next release to pull out the NPE fix we did
on trunk.
Regards
Jörg
Am 26.04.2015 um 11:29 schrieb Jörg Hohwiller:
> Hi,
>
> I'd like to release
Hi there,
I wanted to release the flatten-maven-plugin but the staging repository
is gone in oss.sonatype.org or at least I can not see it anymore.
Can someone shed a light into this?
I can still see the content here:
https://nexus.codehaus.org/content/groups/staging/org/codehaus/mojo/flatten-mave
s gone.
Still hoping for help.
Jörg
Am 01.05.2015 um 09:56 schrieb Dan Tran:
> ATM, Codehaus MOJO does not have a staging repo at Sonatype yet. Your
> staging after promoted will go directly to Maven central
>
> -D
>
> On Fri, May 1, 2015 at 12:41 AM, Jörg Hohwiller <ma
Stupid me. Too many different OSS projects in parallel. For mojo I need
to log in at nexus.sonartype.org and not oss.sonartype.org. Release is
promoted.
Sorry for confusing...
Regards
Jörg
Am 01.05.2015 um 15:46 schrieb Jörg Hohwiller:
> Maybe I used the wrong wording but in the menu there
Hi there,
mvn release:perform failed.
Is codehaus already down for some services?
[INFO] --- maven-site-plugin:3.3:deploy (default-deploy) @
flatten-maven-plugin ---
[INFO] Parent project loaded from repository:
org.codehaus.mojo:mojo-parent:pom:33
[INFO] Parent project loaded from re
This can be a source of inspiration for issue migration:
https://github.com/google/github-issue-mover
Am 12.04.2015 um 23:14 schrieb Jörg Hohwiller:
> Hi there,
>
> I guess jira export is not the problem. GH support for automated
> import will be more of a challange.
> In the wor
90 matches
Mail list logo
