On Sat, Mar 5, 2011 at 3:55 PM, Olivier Lamy wrote:
> So if we activate this new plugin and builds doesn't use anymore the
> option "Deploy artifacts to Maven repository", snapshots will be
> available only in
> https://hudson.apache.org/hudson/plugin/repository/everything or/and
> in the group ht
2011/3/5 Niklas Gustavsson :
> On Sat, Mar 5, 2011 at 3:10 PM, Olivier Lamy wrote:
>> No it will be still possible but not anymore mandatory to provide
>> snapshots for early adopter users.
>
> Not sure I get it. It's currently not mandatory to deploy from your
> Maven build (i.e. running mvn inst
On Sat, Mar 5, 2011 at 3:10 PM, Olivier Lamy wrote:
> No it will be still possible but not anymore mandatory to provide
> snapshots for early adopter users.
Not sure I get it. It's currently not mandatory to deploy from your
Maven build (i.e. running mvn install rather than mvn deploy).
> This g
2011/3/5 Niklas Gustavsson :
> On Sat, Mar 5, 2011 at 12:39 PM, Olivier Lamy wrote:
>> I wonder if we could install this new plugin [1] and add the new
>> snapshot repo generated by this plugin
>> (https://hudson.apache.org/hudson/plugin/repository/everything) as a
>> member of the group
>> https:
On Sat, Mar 5, 2011 at 12:39 PM, Olivier Lamy wrote:
> I wonder if we could install this new plugin [1] and add the new
> snapshot repo generated by this plugin
> (https://hudson.apache.org/hudson/plugin/repository/everything) as a
> member of the group
> https://repository.apache.org/content/grou
oups my bad (sorry for typo)
2011/3/5 Marshall Schor :
>
>
> On 3/5/2011 6:39 AM, Olivier Lamy wrote:
>> I wonder if we could install this new plugin [1] and add the new
>> snapshot repo generated by this plugin
>> (https://hudson.apache.org/hudson/plugin/repository/everything) as a
>> member of t
On 3/5/2011 6:39 AM, Olivier Lamy wrote:
> I wonder if we could install this new plugin [1] and add the new
> snapshot repo generated by this plugin
> (https://hudson.apache.org/hudson/plugin/repository/everything) as a
> member of the group
> https://repository.apache.org/content/groups/public/
I wonder if we could install this new plugin [1] and add the new
snapshot repo generated by this plugin
(https://hudson.apache.org/hudson/plugin/repository/everything) as a
member of the group
https://repository.apache.org/content/groups/public/ .
This will prevent all the current Jenkins MavenRed
On Sat, Mar 5, 2011 at 3:33 AM, Marshall Schor wrote:
> But, in the meanwhile, it would be good to remove this plugin from Jenkins
Done, waiting for a restart
/niklas
Thanks, Olivier,
I will post a Jira to Jenkins about this.
But, in the meanwhile, it would be good to remove this plugin from Jenkins, as
checking it in the Job configure menu makes that menu stop working properly - it
won't show the lower part of the options in the GUI (so once you check it, yo
Hello,
This plugin has been build (as I can see in the sources) with a very
old hudson version 1.301.
The current Jenkins version 1.399 is not anymore backward compatible with.
IMHO the best is to modify Jenkins and the current MavenRedeployer to
prevent deploying SNAPSHOT (this should off by defau
After this plugin (https://issues.apache.org/jira/browse/INFRA-3484) was
installed and this issue closed, I checked the new box that causes this new
plugin to be used, and got an error on the next build.
I went to the job configure screen to "uncheck" the box, and the screen is now
missing the low
On 3/2/2011 9:04 AM, Niklas Gustavsson wrote:
> On Wed, Mar 2, 2011 at 2:32 PM, Scott O'Bryan wrote:
>> You might be right about he "safety" issue but trying to enforce this
>> all the time across all projects is not real feasible. I don't think
>> the plugin would hurt in either case and it pr
On Wed, Mar 2, 2011 at 2:32 PM, Scott O'Bryan wrote:
> You might be right about he "safety" issue but trying to enforce this
> all the time across all projects is not real feasible. I don't think
> the plugin would hurt in either case and it prevents releases from
> getting accidentally uploaded
You might be right about he "safety" issue but trying to enforce this
all the time across all projects is not real feasible. I don't think
the plugin would hurt in either case and it prevents releases from
getting accidentally uploaded to the snapshot repository.
Scott
On Mar 2, 2011, at 6:26 AM
On 2 March 2011 10:27, Marshall Schor wrote:
> If we check the box in a Job configuration that says "Deploy artifacts to the
> Maven Repository" and specify the Apache Nexus Snapshot repo, what happens if
> a
> build starts right at the moment when the Apache Release plugin has renamed
> the
> P
If we check the box in a Job configuration that says "Deploy artifacts to the
Maven Repository" and specify the Apache Nexus Snapshot repo, what happens if a
build starts right at the moment when the Apache Release plugin has renamed the
POMs to a non-Snapshot release version and checked those into
17 matches
Mail list logo
