Re: [DISCUSS] Make Jira issues viewable.

[Bindul Bhowmik]

Hi,

If I may chime in, the Maven (and most Apache) JIRA issues don't
require a login to view. I believe the issue is that Amelia added a
filter to the URL pasted in the tweet, and the filter requires a
login.
So: https://issues.apache.org/jira/browse/MNG-6928 is viewable without
a login https://issues.apache.org/jira/browse/MNG-6928?filter=-2 is
not.

Bindul

On Fri, Sep 11, 2020 at 12:54 AM Maarten Mulders  wrote:
>
> Agreed. If there's anything that is too deliberate to discuss in the
> open, there's the mailing list, direct email or what not.
>
> Maarten
>
> On 11/09/2020 09:51, Robert Scholte wrote:
> > Based on the https://twitter.com/ameliaeiras/status/1303815661307613184 and 
> > the responses of Marten Deinum I agree that it makes sense to make issues 
> > viewable for all.
> >
> > If there is no strong reason to keep it as it is, I'll ask our Jira 
> > administrator if our scheme can be updated.
> > (looks like the Maven projects are missing an explicit Issue Security 
> > scheme)
> >
> > thanks,
> > Robert
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Docker Images

[Bindul Bhowmik]

Maxim,

On Thu, Oct 19, 2017 at 7:54 PM, Maxim Solodovnik  wrote:
>
> Hello,
>
> here is the place for Apache docker images managed by infra and Apache
> projects https://bintray.com/apache/ :)

>From what I have seen, while there are 4 projects with docker
repositories on bintray, there seem to be a lot more at dockerhub [1].
I did a quick search on INFRA JIRA and found that infra has set a few
projects up on dockerhub recently [2], for example INFRA-14756 [3] for
bookkeeper.

Bindul

[1] https://hub.docker.com/r/apache/
[2] 
https://issues.apache.org/jira/issues/?jql=component%20%3D%20Docker%20AND%20project%20%3D%20INFRA
[3] https://issues.apache.org/jira/browse/INFRA-14756

>
> On Fri, Oct 20, 2017 at 12:30 AM, Hervé BOUTEMY 
> wrote:
>
> > great idea
> >
> > ok, we need a git repo at ASF
> >
> > what else?
> > Is there some sort of release process? some sort of source to release?
> >
> > Regards,
> >
> > Hervé
> >
> > Le jeudi 19 octobre 2017, 13:47:45 CEST Mike Drob a écrit :
> > > Thanks for the pointer, Carlos! I had searched the archives, but maybe I
> > > didn't go back far enough.
> > >
> > > I think moving these Dockerfiles into an ASF repo would be great for
> > their
> > > maintainability.
> > >
> > > Thanks,
> > >
> > > Mike
> > >
> > > On 2017-10-19 03:50, Carlos Sanchez  wrote:
> > > > Arnaud is correct, I sent an email to users@ back on Fri, Nov 7,
> > 2014,>
> > > > 00:23 when I created the image>
> > > >
> > > >
> > > > On Thu, Oct 19, 2017, 11:12 Arnaud H�ritier  wrote:>
> > > >
> > > > > These images are kindly managed by a PMC member of our project
> > (Carlos)
> > >
> > > but>
> > >
> > > > > yes they aren't managed directly by the project>
> > > > >
> > > > > We can easily see with him to improve this IMO.>
> > > > >
> > > > > When he started that (several years ago) Docker wasn't what it is
> > >
> > > nowadays.>
> > >
> > > > > With docker being mainstream I agree that we can reconsider this.>
> > > > >
> > > > > The docker image build/distribution could perhaps be part of our
> > >
> > > release>
> > >
> > > > > process.>
> > > > >
> > > > > WDYT Carlos ?>
> > > > >
> > > > > On Thu, Oct 19, 2017 at 4:16 AM, Mike Drob 
> > wrote:>
> > > > >
> > > > > > I guess the natural follow-on question is whether the Maven
> > >
> > > community>
> > >
> > > > > > would consider publishing an official set of images? Or
> > >
> > > alternatively>
> > >
> > > > > > whether they should send a takedown notice to protect their brand
> > >
> > > and>
> > >
> > > > > > trademarks...>
> > > > > >
> > > > > > On 2017-10-18 18:36, "Manfred Moser" 
> > wrote:>
> > > > > >
> > > > > > > No. As you can see from the github URL this is NOT an apache
> > URL.>
> > > > > > >
> > > > > > > https://github.com/carlossg/docker-maven>
> > > > > > >
> > > > > > >
> > > > > > > Mike Drob wrote on 2017-10-18 16:32:>
> > > > > > >
> > > > > > > > Hello,>
> > > > > > > >
> > > > > > > > Are the images at https://hub.docker.com/r/_/maven/
> > considered to
> > >
> > > be>
> > >
> > > > > > official>
> > > > > >
> > > > > > > > maven docker images and blessed/published by the PMC?>
> > > > > > > >
> > > > > > > > Thanks,>
> > > > > > > > Mike>
> > >
> > > ->
> > >
> > > > > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org>
> > > > > > > > For additional commands, e-mail: users-h...@maven.apache.org>
> > >
> > > ->
> > >
> > > > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org>
> > > > > > > For additional commands, e-mail: users-h...@maven.apache.org>
> > >
> > > ->
> > >
> > > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org>
> > > > > > For additional commands, e-mail: users-h...@maven.apache.org>
> > > > >
> > > > > -->
> > > > > ->
> > > > > Arnaud H�ritier>
> > > > > http://aheritier.net>
> > > > > Mail/GTalk: aheritier AT gmail DOT com>
> > > > > Twitter/Skype : aheritier>
> >
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
>
> --
> WBR
> Maxim aka solomax

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Migration of remaining plugins to Git

[Bindul Bhowmik]

Paul,

On Mon, Jun 19, 2017 at 12:42 PM, Paul Hammant  wrote:
> Back from Github's suggestions team: "Currently, we don't have the ability
> to group repos beyond the organization level, but I'll definitely consider
> this a feature request."

Until such time, how about grouping the repositories by name, like
https://github.com/apache/maven-plugin-

A number of other projects in Apache have done this, for example
https://git-wip-us.apache.org/repos/asf?a=project_list=incubator-predictionio
or https://gitbox.apache.org/repos/asf?a=project_list=incubator-openwhisk

- Bindul

>
> - Paul
>
> On Sun, Jun 18, 2017 at 7:04 PM, Paul Hammant  wrote:
>>
>> I met Chris Wanstrath at a meetup in Cincinatti about four years ago, and
>> bent his ear about how fantastic Github-Pages (and Jekyll) was as a CMS. I
>> suggested that if they could add themes for "high school", "community
>> group", etc they could pull in another category of user of the platform, and
>> that the themes that are available for gh-pages are not that useful as they
>> are.
>>
>>
>>
>> ^ screencap from today: unchanged :(
>>
>> On Sun, Jun 18, 2017 at 6:46 PM, Stephen Connolly
>>  wrote:
>>>
>>> Polite, yes, just non commital ;-)
>>>
>>> On Sun 18 Jun 2017 at 23:10, Paul Hammant  wrote:
>>>
>>> > They're always very polite for things that I ask for, but I can't claim
>>> > to
>>> > have suggested anything that got implemented. I've a better hit-rate
>>> > with
>>> > JetBrains and their IDEs.
>>> >
>>> > - Paul
>>> >
>>> > On Sun, Jun 18, 2017 at 4:39 PM, Stephen Connolly <
>>> > stephen.alan.conno...@gmail.com> wrote:
>>> >
>>> > > Liable to get an answer like:
>>> > >
>>> > > > We don't comment our roadmap publicly I'm afraid
>>> > >
>>> > > (I've gotten that a couple of times for different things... you'd
>>> > > think
>>> > > given that I'm the maintainer of the GitHub Branch Source plugin for
>>> > > Jenkins they might - you know - want to help... but alas)
>>> > >
>>> > > On 18 June 2017 at 10:12, Paul Hammant  wrote:
>>> > >
>>> > > > Good thought. We could ask about a timeline.
>>> > > >
>>> > > > On Sun, Jun 18, 2017 at 1:00 PM, Stephen Connolly <
>>> > > > stephen.alan.conno...@gmail.com> wrote:
>>> > > >
>>> > > > > They are now adding user grouping... I wonder how long before
>>> > > > > repo
>>> > > > grouping
>>> > > > > too
>>> > > > >
>>> > > > > On Sun 18 Jun 2017 at 17:12, Paul Hammant 
>>> > > > > wrote:
>>> > > > >
>>> > > > > > Choose one to start with, is what I would do.
>>> > > > > >
>>> > > > > > git svn clone of a trunk only, then make that master.
>>> > > > > > branch/tag
>>> > > > history
>>> > > > > > can be retained in Subversion but also up on MavenCentral as
>>> > > > > > foo-x.y-sources.jar files.  Unless you optimize that
>>> > > > > > git-svn-clone
>>> > > > > > operation by specifying the first Svn commit for the module in
>>> > > > question,
>>> > > > > > it'll need many hours to iterate over all commits to pluck out
>>> > > > > > the
>>> > > ones
>>> > > > > > pertinent to the trunk of that module.
>>> > > > > >
>>> > > > > > GitHub only allows a single effective 'parent directory' for
>>> > > > > > repos,
>>> > > so
>>> > > > > > instead of the general github.com/apache org (and in lieu of
>>> > > > > > github.com/apache/maven/ which is what you'd
>>> > > > > > actually
>>> > > > want),
>>> > > > > we
>>> > > > > > could do github.com/apache-maven/.
>>> > > > > >
>>> > > > > > I volunteer for some of the work.  Err, maybe I should read
>>> > > > > > those
>>> > > > > > confluence pages.
>>> > > > > >
>>> > > > > > - Paul
>>> > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > > > On Sun, Jun 18, 2017 at 11:51 AM, Hervé BOUTEMY <
>>> > > herve.bout...@free.fr
>>> > > > >
>>> > > > > > wrote:
>>> > > > > >
>>> > > > > > > yes, git is really ubiquitous now and nowadays could perhaps
>>> > > > > > > help
>>> > > > some
>>> > > > > > > contributions
>>> > > > > > > here is our tracking of git migration [1]
>>> > > > > > >
>>> > > > > > > there are a few entries that we could move if someone takes
>>> > > > > > > the
>>> > > job:
>>> > > > > > > Doxia core, Doxia Site Tools, Enforcer, Jxr, Plugin Tools,
>>> > Release
>>> > > > > > >
>>> > > > > > > there are issues to fix when migrating 1 svn repo
>>> > > (trunk/tags/branch)
>>> > > > > to
>>> > > > > > > many
>>> > > > > > > git repos that are documented but not solved yet
>>> > > > > > > Plugins and shared components are the 2 big repos, with
>>> > > respectively
>>> > > > 41
>>> > > > > > > and 26
>>> > > > > > > parts if we switch to git that look hard to manage if we
>>> > > > > > > don't
>>> > > have a
>>> > > > > > plan.
>>> > > > > > > Perphaps Jenkins pipelines could provide some solutions on
>>> > > > > > > the
>>> > > > Jenkins
>>> > > > > > > side.
>>> > > > > > >
>>> > > > > > > Skins is perhaps not an issue any more now that we 

Re: Configurable Dependencies for Maven Plugins?

[Bindul Bhowmik]

Dirk,

On Wed, Apr 12, 2017 at 7:06 AM, Dirk Mahler  wrote:
> Hi all,
>
> is there a way to provide users of a plugin a way of easily switching
> dependencies of it?
>
> Background: I'm developing a Maven plugin (jQAssistant) that comes with a
> dependency to Neo4j (graph database). Currently I'm using Neo4j 2.3.x which
> has been compiled against Java 7 but I would like to offer users of the
> Maven plugin an easy option to use the newer Neo4j 3.x releases which offer
> some new features but require Java 8.
>
> I know that it's possible to overwrite an existing dependency for a plugin,
> e.g.
>
> 
>   com.buschmais.jqassistant
>   jqassistant-maven-plugin
>   1.3.0
>   
> 
>   org.neo4j
>   neo4j
>   3.1.3 
> 
>   
> 

As long as your code can handle the different versions of the
dependency, I think this is absolutely doable. In fact the Maven
Checkstyle Plugin uses the same approach to allow upgrading checkstyle
versions without upgrading the plugin version [1].

>
> The problem is that in my case the old version comes with another set of
> dependencies than the new one:

I do not think this will be a problem.

>
> old:
>
> 
>  
>  org.neo4j
>  neo4j
>  2.3.10
>  
>  
>  org.neo4j.app
>  neo4j-server
>  2.3.10
>  
>  
>  org.neo4j.app
>  neo4j-server
>  static-web
>  2.3.10
>  
> 
>
> new:
>
> 
>  
>  org.neo4j
>  neo4j
>  3.1.3
>  
>  
>  org.neo4j.app
>  neo4j-server
>  3.1.3
>  
> 
>
> Is there a good way to deal with it such that a user of the
> jqassistant-maven-plugin can easily switch between both variants?
>
> Cheers,
>
> Dirk
>
> Senior Consultant IT
> buschmais GbR


- Bindul

[1] 
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html

>
> -
> Inhaber Torsten Busch, Frank Schwarz, Dirk Mahler, Tobias Israel
> Adresse buschmais GbR, Leipziger Straße 93, 01127 Dresden
> Telefon  +49 (0) 351 3209 23-0
> Fax  +49 (0) 351 3209 23-29
> Mobil+49 (0) 177 3137411
> E-Mail   dirk.mah...@buschmais.com
> Internet http://www.buschmais.de
> -
>
> Diese E-Mail enthält vertrauliche undoder rechtlich geschützte
> Informationen. Wenn Sie diese E-Mail irrtümlich erhalten haben,
> bitten wir Sie diese E-Mail umgehend zu löschen. Das unerlaubte
> Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht
> gestattet.
>
> This e-mail may contain confidential or privileged information. If
> you are not the intended recipient we kindly request you to delete
> this e-mail immediately. Any unauthorized copying, disclosure or
> distribution of the material in this e-mail is strictly forbidden.
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org