Issue with maven depentencies

2018-10-12 Thread Alexius DIAKOGIANNIS 
Hi,

I have stumbled upon this strange issue.

I am installing a jar from console, for example

mvn install:install-file -Dfile=wlclient.jar -DgroupId=com.oracle.weblogic
-DartifactId=wlclient -Dversion=12.1.3.0 -Dpackaging=jar

When I building from Netbeans 8.2 maven cannot resolve the dependency. When
I am building from console everything is fine.

Any ideas?

Thanks

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread William L. Thomson Jr. 
On Wed, 3 Oct 2018 07:14:58 +0200
Geertjan Wielenga  wrote:

> No

YES

> the Apache terminology is voting candidate.

Just because Apache terminology is voting candidate. That does not mean
it should be tagged as such. I package quite a few Apache projects.
NONE use this crazy format of -vc*. Most Apache release are voted on.

Please stick with common stuff, dev, alpha, beta, pre. For releases
there should be NO additional suffix.

> On Wed, Oct 3, 2018 at 7:06 AM László Kishalmi
>  wrote:
> 
> > I meant: I'm not sure that we need to vote on this. It's more like
> > a beta. Shouldn't we have called it beta at first? Just for the
> > further release processes...

Yes it should be a -beta or -pre, or something standard...

Examples of other Apache release that were voted on and released
without crazy tags

You can see Votes
https://www.mail-archive.com/dev@maven.apache.org/

No crazy -vc tags
https://github.com/apache/maven-resolver/releases
https://github.com/apache/maven/releases

Some more apache projects
https://github.com/apache/tomcat/releases
https://github.com/apache/ant/releases
https://github.com/apache/commons-pool/releases
https://github.com/apache/commons-logging/releases

I have never seen any Apache project use -vc for tagging a vote
candidate. They may exist, but the first time I recall seeing this was
with Apache Netbeans. Can anyone find another Apache project that has
-vc tags? If not then why is Netbeans doing this?

This is what I had to do for 9.0. Nasty hidden change of version.
https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/eclass/java-netbeans.eclass#L17

I have to do something similar for 10.0-vc1. Which I also have to add
some other prefix, as I cannot use 10.0 -> 10.0-vc1 like I do for 9.0.
As 10 is not fully released, there maybe another 10.0-vc*

On github seems like 9.0 was never released What is the difference
between 9.0-vc* and 10.0-vc* ? Which one the release?  Which one is
just a voting candidate?
https://github.com/apache/incubator-netbeans/releases

If you must continue on with -vc tags. Please create another non -vc
tag for the actual release. You can have more than one tag for a given
commit. But really the -vc stuff is just confusing. It seems only
Netbeans is using this odd format. It is not standard.

-- 
William L. Thomson Jr.

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

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread Geertjan Wielenga 
See the below:

https://lists.apache.org/thread.html/692fee91f7e24dcfffa099593c758772216d130c21ca97c689a294f8@%3Cdev.netbeans.apache.org%3E

We've ended up following guidance from our mentors, there are simply too
many conflicting points of view throughout Apache.

The craziness had to stop and so we're following the guidelines our Apache
mentors have provided.

Thanks,

Gj




On Fri, Oct 12, 2018 at 7:46 PM William L. Thomson Jr. 
wrote:

> On Wed, 3 Oct 2018 07:14:58 +0200
> Geertjan Wielenga  wrote:
>
> > No
>
> YES
>
> > the Apache terminology is voting candidate.
>
> Just because Apache terminology is voting candidate. That does not mean
> it should be tagged as such. I package quite a few Apache projects.
> NONE use this crazy format of -vc*. Most Apache release are voted on.
>
> Please stick with common stuff, dev, alpha, beta, pre. For releases
> there should be NO additional suffix.
>
> > On Wed, Oct 3, 2018 at 7:06 AM László Kishalmi
> >  wrote:
> >
> > > I meant: I'm not sure that we need to vote on this. It's more like
> > > a beta. Shouldn't we have called it beta at first? Just for the
> > > further release processes...
>
> Yes it should be a -beta or -pre, or something standard...
>
> Examples of other Apache release that were voted on and released
> without crazy tags
>
> You can see Votes
> https://www.mail-archive.com/dev@maven.apache.org/
>
> No crazy -vc tags
> https://github.com/apache/maven-resolver/releases
> https://github.com/apache/maven/releases
>
> Some more apache projects
> https://github.com/apache/tomcat/releases
> https://github.com/apache/ant/releases
> https://github.com/apache/commons-pool/releases
> https://github.com/apache/commons-logging/releases
>
> I have never seen any Apache project use -vc for tagging a vote
> candidate. They may exist, but the first time I recall seeing this was
> with Apache Netbeans. Can anyone find another Apache project that has
> -vc tags? If not then why is Netbeans doing this?
>
> This is what I had to do for 9.0. Nasty hidden change of version.
>
> https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/eclass/java-netbeans.eclass#L17
>
> I have to do something similar for 10.0-vc1. Which I also have to add
> some other prefix, as I cannot use 10.0 -> 10.0-vc1 like I do for 9.0.
> As 10 is not fully released, there maybe another 10.0-vc*
>
> On github seems like 9.0 was never released What is the difference
> between 9.0-vc* and 10.0-vc* ? Which one the release?  Which one is
> just a voting candidate?
> https://github.com/apache/incubator-netbeans/releases
>
> If you must continue on with -vc tags. Please create another non -vc
> tag for the actual release. You can have more than one tag for a given
> commit. But really the -vc stuff is just confusing. It seems only
> Netbeans is using this odd format. It is not standard.
>
> --
> William L. Thomson Jr.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread William L. Thomson Jr. 
On Fri, 12 Oct 2018 19:48:46 +0200
Geertjan Wielenga  wrote:

> See the below:
> 
> https://lists.apache.org/thread.html/692fee91f7e24dcfffa099593c758772216d130c21ca97c689a294f8@%3Cdev.netbeans.apache.org%3E
> 
> We've ended up following guidance from our mentors, there are simply
> too many conflicting points of view throughout Apache.

Why do NO other Apache projects follow this tagging format? Why is this
being imposed on only Netbeans? Who at Apache can I contact to get this
resolved?

> The craziness had to stop and so we're following the guidelines our
> Apache mentors have provided.

They are the ones causing the craziness. That email, link provided
above, should include a link to an official Apache policy on tags. That
seems more like one persons opinion than an official Apache policy.

This says nothing about -vc tags or any tags as part of voting or
release process
https://www.apache.org/foundation/voting.html
https://www.apache.org/foundation/voting.html#ReleaseVotes

In fact if you follow into the glossary it clearly states votes should
be on release candidates It literally states to be voted on
https://www.apache.org/foundation/glossary.html#ReleaseCandidate

No other incubating projects have those crazy -vc tags. I cannot find a
single Apache project that has -vc tags. I would push back on these so
called Mentors

https://github.com/apache/incubator-dubbo/releases
https://github.com/apache/incubator-echarts/releases
https://github.com/apache/incubator-mxnet/releases
https://github.com/apache/incubator-superset/releases
https://github.com/apache/incubator-airflow/releases

There are a lot more incubating projects. I am seriously trying to find
another Apache project with -vc tags so there is some justification.


> Thanks,
> 
> Gj
> 
> 
> 
> 
> On Fri, Oct 12, 2018 at 7:46 PM William L. Thomson Jr.
>  wrote:
> 
> > On Wed, 3 Oct 2018 07:14:58 +0200
> > Geertjan Wielenga  wrote:
> >  
> > > No  
> >
> > YES
> >  
> > > the Apache terminology is voting candidate.  
> >
> > Just because Apache terminology is voting candidate. That does not
> > mean it should be tagged as such. I package quite a few Apache
> > projects. NONE use this crazy format of -vc*. Most Apache release
> > are voted on.
> >
> > Please stick with common stuff, dev, alpha, beta, pre. For releases
> > there should be NO additional suffix.
> >  
> > > On Wed, Oct 3, 2018 at 7:06 AM László Kishalmi
> > >  wrote:
> > >  
> > > > I meant: I'm not sure that we need to vote on this. It's more
> > > > like a beta. Shouldn't we have called it beta at first? Just
> > > > for the further release processes...  
> >
> > Yes it should be a -beta or -pre, or something standard...
> >
> > Examples of other Apache release that were voted on and released
> > without crazy tags
> >
> > You can see Votes
> > https://www.mail-archive.com/dev@maven.apache.org/
> >
> > No crazy -vc tags
> > https://github.com/apache/maven-resolver/releases
> > https://github.com/apache/maven/releases
> >
> > Some more apache projects
> > https://github.com/apache/tomcat/releases
> > https://github.com/apache/ant/releases
> > https://github.com/apache/commons-pool/releases
> > https://github.com/apache/commons-logging/releases
> >
> > I have never seen any Apache project use -vc for tagging a vote
> > candidate. They may exist, but the first time I recall seeing this
> > was with Apache Netbeans. Can anyone find another Apache project
> > that has -vc tags? If not then why is Netbeans doing this?
> >
> > This is what I had to do for 9.0. Nasty hidden change of version.
> >
> > https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/eclass/java-netbeans.eclass#L17
> >
> > I have to do something similar for 10.0-vc1. Which I also have to
> > add some other prefix, as I cannot use 10.0 -> 10.0-vc1 like I do
> > for 9.0. As 10 is not fully released, there maybe another
> > 10.0-vc*
> >
> > On github seems like 9.0 was never released What is the
> > difference between 9.0-vc* and 10.0-vc* ? Which one the release?
> > Which one is just a voting candidate?
> > https://github.com/apache/incubator-netbeans/releases
> >
> > If you must continue on with -vc tags. Please create another non -vc
> > tag for the actual release. You can have more than one tag for a
> > given commit. But really the -vc stuff is just confusing. It seems
> > only Netbeans is using this odd format. It is not standard.
> >
> > --
> > William L. Thomson Jr.
> >
> > -
> > To unsubscribe, e-mail:
> > dev-unsubscr...@netbeans.incubator.apache.org For additional
> > commands, e-mail: dev-h...@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >  



-- 
William L. Thomson Jr.

-
To unsubscribe, e-mail: dev-

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread Geertjan Wielenga 
Just bear in mind that we're new to all this. Can you tone down your
exasperation and try to bear that in mind?

I think we should definitely revisit this, if it's causing problems and
confusion, we could start a new thread to discuss this.

Also, can you join this mailing list, right now I have to moderate each
mail you send, and I'm not always on-line, so sometimes it's going to be
even more exasperating to you, to see your messages not appearing here.

Gj


On Fri, Oct 12, 2018 at 8:05 PM William L. Thomson Jr. 
wrote:

> On Fri, 12 Oct 2018 19:48:46 +0200
> Geertjan Wielenga  wrote:
>
> > See the below:
> >
> >
> https://lists.apache.org/thread.html/692fee91f7e24dcfffa099593c758772216d130c21ca97c689a294f8@%3Cdev.netbeans.apache.org%3E
> >
> > We've ended up following guidance from our mentors, there are simply
> > too many conflicting points of view throughout Apache.
>
> Why do NO other Apache projects follow this tagging format? Why is this
> being imposed on only Netbeans? Who at Apache can I contact to get this
> resolved?
>
> > The craziness had to stop and so we're following the guidelines our
> > Apache mentors have provided.
>
> They are the ones causing the craziness. That email, link provided
> above, should include a link to an official Apache policy on tags. That
> seems more like one persons opinion than an official Apache policy.
>
> This says nothing about -vc tags or any tags as part of voting or
> release process
> https://www.apache.org/foundation/voting.html
> https://www.apache.org/foundation/voting.html#ReleaseVotes
>
> In fact if you follow into the glossary it clearly states votes should
> be on release candidates It literally states to be voted on
> https://www.apache.org/foundation/glossary.html#ReleaseCandidate
>
> No other incubating projects have those crazy -vc tags. I cannot find a
> single Apache project that has -vc tags. I would push back on these so
> called Mentors
>
> https://github.com/apache/incubator-dubbo/releases
> https://github.com/apache/incubator-echarts/releases
> https://github.com/apache/incubator-mxnet/releases
> https://github.com/apache/incubator-superset/releases
> https://github.com/apache/incubator-airflow/releases
>
> There are a lot more incubating projects. I am seriously trying to find
> another Apache project with -vc tags so there is some justification.
>
>
> > Thanks,
> >
> > Gj
> >
> >
> >
> >
> > On Fri, Oct 12, 2018 at 7:46 PM William L. Thomson Jr.
> >  wrote:
> >
> > > On Wed, 3 Oct 2018 07:14:58 +0200
> > > Geertjan Wielenga  wrote:
> > >
> > > > No
> > >
> > > YES
> > >
> > > > the Apache terminology is voting candidate.
> > >
> > > Just because Apache terminology is voting candidate. That does not
> > > mean it should be tagged as such. I package quite a few Apache
> > > projects. NONE use this crazy format of -vc*. Most Apache release
> > > are voted on.
> > >
> > > Please stick with common stuff, dev, alpha, beta, pre. For releases
> > > there should be NO additional suffix.
> > >
> > > > On Wed, Oct 3, 2018 at 7:06 AM László Kishalmi
> > > >  wrote:
> > > >
> > > > > I meant: I'm not sure that we need to vote on this. It's more
> > > > > like a beta. Shouldn't we have called it beta at first? Just
> > > > > for the further release processes...
> > >
> > > Yes it should be a -beta or -pre, or something standard...
> > >
> > > Examples of other Apache release that were voted on and released
> > > without crazy tags
> > >
> > > You can see Votes
> > > https://www.mail-archive.com/dev@maven.apache.org/
> > >
> > > No crazy -vc tags
> > > https://github.com/apache/maven-resolver/releases
> > > https://github.com/apache/maven/releases
> > >
> > > Some more apache projects
> > > https://github.com/apache/tomcat/releases
> > > https://github.com/apache/ant/releases
> > > https://github.com/apache/commons-pool/releases
> > > https://github.com/apache/commons-logging/releases
> > >
> > > I have never seen any Apache project use -vc for tagging a vote
> > > candidate. They may exist, but the first time I recall seeing this
> > > was with Apache Netbeans. Can anyone find another Apache project
> > > that has -vc tags? If not then why is Netbeans doing this?
> > >
> > > This is what I had to do for 9.0. Nasty hidden change of version.
> > >
> > >
> https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/eclass/java-netbeans.eclass#L17
> > >
> > > I have to do something similar for 10.0-vc1. Which I also have to
> > > add some other prefix, as I cannot use 10.0 -> 10.0-vc1 like I do
> > > for 9.0. As 10 is not fully released, there maybe another
> > > 10.0-vc*
> > >
> > > On github seems like 9.0 was never released What is the
> > > difference between 9.0-vc* and 10.0-vc* ? Which one the release?
> > > Which one is just a voting candidate?
> > > https://github.com/apache/incubator-netbeans/releases
> > >
> > > If you must continue on with -vc tags. Please create another non -vc
> > > tag for the actual release.

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread Geertjan Wielenga 
I think the main problem we're trying to solve with the -vc tag is this:
what happens when we start a vote thread and the vote fails for some
reason? Then we need to make a new voting candidate and start a new vote
thread. How do we name these artefacts, i.e., how do we distinguish between
them?

If you have advice here, in a way that would solve this for us, as well as
you, that would be wonderful. Ideally, just leave the exasperation aside
(for which we apologize) and just explain how we can solve this, and we'll
do it.

FYI, the question "Who at Apache can I contact to get this resolved?" is
always going to be "Start a new proposal on the dev mailing list and
discuss your ideas, reach a consensus, and in a worst case scenario, we'll
vote on it."

Thanks,

Gj


On Fri, Oct 12, 2018 at 8:07 PM Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> Just bear in mind that we're new to all this. Can you tone down your
> exasperation and try to bear that in mind?
>
> I think we should definitely revisit this, if it's causing problems and
> confusion, we could start a new thread to discuss this.
>
> Also, can you join this mailing list, right now I have to moderate each
> mail you send, and I'm not always on-line, so sometimes it's going to be
> even more exasperating to you, to see your messages not appearing here.
>
> Gj
>
>
> On Fri, Oct 12, 2018 at 8:05 PM William L. Thomson Jr. 
> wrote:
>
>> On Fri, 12 Oct 2018 19:48:46 +0200
>> Geertjan Wielenga  wrote:
>>
>> > See the below:
>> >
>> >
>> https://lists.apache.org/thread.html/692fee91f7e24dcfffa099593c758772216d130c21ca97c689a294f8@%3Cdev.netbeans.apache.org%3E
>> >
>> > We've ended up following guidance from our mentors, there are simply
>> > too many conflicting points of view throughout Apache.
>>
>> Why do NO other Apache projects follow this tagging format? Why is this
>> being imposed on only Netbeans? Who at Apache can I contact to get this
>> resolved?
>>
>> > The craziness had to stop and so we're following the guidelines our
>> > Apache mentors have provided.
>>
>> They are the ones causing the craziness. That email, link provided
>> above, should include a link to an official Apache policy on tags. That
>> seems more like one persons opinion than an official Apache policy.
>>
>> This says nothing about -vc tags or any tags as part of voting or
>> release process
>> https://www.apache.org/foundation/voting.html
>> https://www.apache.org/foundation/voting.html#ReleaseVotes
>>
>> In fact if you follow into the glossary it clearly states votes should
>> be on release candidates It literally states to be voted on
>> https://www.apache.org/foundation/glossary.html#ReleaseCandidate
>>
>> No other incubating projects have those crazy -vc tags. I cannot find a
>> single Apache project that has -vc tags. I would push back on these so
>> called Mentors
>>
>> https://github.com/apache/incubator-dubbo/releases
>> https://github.com/apache/incubator-echarts/releases
>> https://github.com/apache/incubator-mxnet/releases
>> https://github.com/apache/incubator-superset/releases
>> https://github.com/apache/incubator-airflow/releases
>>
>> There are a lot more incubating projects. I am seriously trying to find
>> another Apache project with -vc tags so there is some justification.
>>
>>
>> > Thanks,
>> >
>> > Gj
>> >
>> >
>> >
>> >
>> > On Fri, Oct 12, 2018 at 7:46 PM William L. Thomson Jr.
>> >  wrote:
>> >
>> > > On Wed, 3 Oct 2018 07:14:58 +0200
>> > > Geertjan Wielenga  wrote:
>> > >
>> > > > No
>> > >
>> > > YES
>> > >
>> > > > the Apache terminology is voting candidate.
>> > >
>> > > Just because Apache terminology is voting candidate. That does not
>> > > mean it should be tagged as such. I package quite a few Apache
>> > > projects. NONE use this crazy format of -vc*. Most Apache release
>> > > are voted on.
>> > >
>> > > Please stick with common stuff, dev, alpha, beta, pre. For releases
>> > > there should be NO additional suffix.
>> > >
>> > > > On Wed, Oct 3, 2018 at 7:06 AM László Kishalmi
>> > > >  wrote:
>> > > >
>> > > > > I meant: I'm not sure that we need to vote on this. It's more
>> > > > > like a beta. Shouldn't we have called it beta at first? Just
>> > > > > for the further release processes...
>> > >
>> > > Yes it should be a -beta or -pre, or something standard...
>> > >
>> > > Examples of other Apache release that were voted on and released
>> > > without crazy tags
>> > >
>> > > You can see Votes
>> > > https://www.mail-archive.com/dev@maven.apache.org/
>> > >
>> > > No crazy -vc tags
>> > > https://github.com/apache/maven-resolver/releases
>> > > https://github.com/apache/maven/releases
>> > >
>> > > Some more apache projects
>> > > https://github.com/apache/tomcat/releases
>> > > https://github.com/apache/ant/releases
>> > > https://github.com/apache/commons-pool/releases
>> > > https://github.com/apache/commons-logging/releases
>> > >
>> > > I have never seen any Apache project use -vc for tagging a

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread William L. Thomson Jr. 
On Fri, 12 Oct 2018 20:07:45 +0200
Geertjan Wielenga  wrote:

> Just bear in mind that we're new to all this. Can you tone down your
> exasperation and try to bear that in mind?

Sorry, but I have repeatedly brought up this issue.
https://lists.apache.org/thread.html/d31294f296a99d7379ca4ca78a8a5ec33bd12f6a7e365b2e67182a05@%3Cdev.netbeans.apache.org%3E
https://lists.apache.org/thread.html/1c3a1af37c49baeb1e29664999f826d298316fa3eaa97656ac46d1cf@%3Cdev.netbeans.apache.org%3E

> I think we should definitely revisit this, if it's causing problems
> and confusion, we could start a new thread to discuss this.

I have... It feel on deaf ears
https://lists.apache.org/thread.html/2aedd00af7ae24b8b4c23f62afeacbaeeb9ea22145252b1d2638df3c@%3Cdev.netbeans.apache.org%3E

That was a simple request for a duplicate tag... Can you see where the
frustration comes from ~6 months of trying to correct tags. I can make
another to discuss the tagging. I feel we have covered this several
times already though

> Also, can you join this mailing list, right now I have to moderate
> each mail you send, and I'm not always on-line, so sometimes it's
> going to be even more exasperating to you, to see your messages not
> appearing here.

I have repeatedly... I get emails which means I should be subscribed. I
will subscribe again. No clue how I am getting list posts without being
subscribed :)

I have been removed in the past automatically due to bounced emails.
Though that does not happen on other lists. Occasionally I get a warning
usually from JClouds mailing list. Never from Maven, or Tomcat when I
was on Tomcat dev list.


-- 
William L. Thomson Jr.

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

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread William L. Thomson Jr. 
On Fri, 12 Oct 2018 20:21:17 +0200
Geertjan Wielenga  wrote:

> I think the main problem we're trying to solve with the -vc tag is
> this: what happens when we start a vote thread and the vote fails for
> some reason? Then we need to make a new voting candidate and start a
> new vote thread. How do we name these artefacts, i.e., how do we
> distinguish between them?

Per Apache documentation, you create a new release candidate.
https://www.apache.org/foundation/glossary.html#ReleaseCandidate

Why some projects have multiple rc* without an actual release. It
likely has not passed that process yet.
 
> If you have advice here, in a way that would solve this for us, as
> well as you, that would be wonderful. Ideally, just leave the
> exasperation aside (for which we apologize) and just explain how we
> can solve this, and we'll do it.

Just like other projects, use RC for a release candidate. Vote on that,
and increment RC as necessary till a vote passes. Once a vote
passes. Then you re-tag for a release without RC. I feel its standard
for most any project Apache or not.
https://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate

They just omit any reference to Voting in Wikipedia, as it is likely
less standard. Not all software is released after a vote.

> FYI, the question "Who at Apache can I contact to get this resolved?"
> is always going to be "Start a new proposal on the dev mailing list
> and discuss your ideas, reach a consensus, and in a worst case
> scenario, we'll vote on it."

Seemed it was mentors who were imposing this -vc, not the community.
Thus I was asking which mentors, or how to contact them to discuss it
directly. It seems mentors are misleading on project direction
regarding release process and tagging.

-- 
William L. Thomson Jr.


pgpJXJ27fZgB6.pgp
Description: OpenPGP digital signature

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread Geertjan Wielenga 
No one imposed anything. No, contacting mentors and discussing with
individual people off-thread is not how Apache projects work.

We have a long history in NetBeans outside Apache where we used the term
'release candidate' to mean something very different to how it is used in
Apache, i.e., an overloading of terms. This was a way to resolve it
suggested by our mentors.

And, you're not subscribed to this mailing lisy, I keep needing to moderate
you, I don't know why. But when you're not seeing your e-mails here, it
means I'm not on-line to moderate them.

I apologize for no one responding to those previous e-mails -- I skipped
over them because I think the right approach here in an Apache project is
to start a new thread with [PROPOSAL] or [DISCUSS] or something like that,
i.e., what you're asking for is actually a new tagging strategy, rather
than for a tag to be created with no suffix for a specific release.

I also don't understand the entire context -- and having everything hidden
in e-mails doesn't help either. For example, Laszlo created this, if you
were to create something similar we'd all have a better idea what we're
talking about:

https://cwiki.apache.org/confluence/display/NETBEANS/Public+vs+Friend+API

Gj

On Fri, Oct 12, 2018 at 8:29 PM William L. Thomson Jr. 
wrote:

> On Fri, 12 Oct 2018 20:21:17 +0200
> Geertjan Wielenga  wrote:
>
> > I think the main problem we're trying to solve with the -vc tag is
> > this: what happens when we start a vote thread and the vote fails for
> > some reason? Then we need to make a new voting candidate and start a
> > new vote thread. How do we name these artefacts, i.e., how do we
> > distinguish between them?
>
> Per Apache documentation, you create a new release candidate.
> https://www.apache.org/foundation/glossary.html#ReleaseCandidate
>
> Why some projects have multiple rc* without an actual release. It
> likely has not passed that process yet.
>
> > If you have advice here, in a way that would solve this for us, as
> > well as you, that would be wonderful. Ideally, just leave the
> > exasperation aside (for which we apologize) and just explain how we
> > can solve this, and we'll do it.
>
> Just like other projects, use RC for a release candidate. Vote on that,
> and increment RC as necessary till a vote passes. Once a vote
> passes. Then you re-tag for a release without RC. I feel its standard
> for most any project Apache or not.
> https://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate
>
> They just omit any reference to Voting in Wikipedia, as it is likely
> less standard. Not all software is released after a vote.
>
> > FYI, the question "Who at Apache can I contact to get this resolved?"
> > is always going to be "Start a new proposal on the dev mailing list
> > and discuss your ideas, reach a consensus, and in a worst case
> > scenario, we'll vote on it."
>
> Seemed it was mentors who were imposing this -vc, not the community.
> Thus I was asking which mentors, or how to contact them to discuss it
> directly. It seems mentors are misleading on project direction
> regarding release process and tagging.
>
> --
> William L. Thomson Jr.
>

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread William L. Thomson Jr. 
On Fri, 12 Oct 2018 20:31:53 +0200
Geertjan Wielenga  wrote:

> No one imposed anything. No, contacting mentors and discussing with
> individual people off-thread is not how Apache projects work.
> 
> We have a long history in NetBeans outside Apache where we used the
> term 'release candidate' to mean something very different to how it
> is used in Apache, i.e., an overloading of terms. This was a way to
> resolve it suggested by our mentors.

That makes a bit more sense then. You did say in a previous post that
it came from mentors. I did not understand it was advised by mentors as
means to continue how Netbeans releases were handled before the move to
Apache. Or some compromise.

> And, you're not subscribed to this mailing lisy, I keep needing to
> moderate you, I don't know why. But when you're not seeing your
> e-mails here, it means I'm not on-line to moderate them.

I was using wrong email. I have an email address specific for posting
to lists I was not using. Thus receiving but sending under the wrong
one. Very sorry!!! Thanks for forwarding on those posts!

> I apologize for no one responding to those previous e-mails -- I
> skipped over them because I think the right approach here in an
> Apache project is to start a new thread with [PROPOSAL] or [DISCUSS]
> or something like that, i.e., what you're asking for is actually a
> new tagging strategy, rather than for a tag to be created with no
> suffix for a specific release.

I have asked for both, either a change to the current strategy. Or a
simple duplicate tag. Which I felt was a compromise to satisfy all.

> I also don't understand the entire context -- and having everything
> hidden in e-mails doesn't help either. For example, Laszlo created
> this, if you were to create something similar we'd all have a better
> idea what we're talking about:

 I can see about creating a wiki page to cover the tagging of Netbeans.
 Not sure if that will help or not. I just assumed tagging software and
 the various suffixes were well known. I am just asking for things to
 be standardize.

This pretty much covers it all
https://en.wikipedia.org/wiki/Software_release_life_cycle

The diagram enough should be suffice
https://en.wikipedia.org/wiki/Software_release_life_cycle#/media/File:Software_dev2.svg

-- 
William L. Thomson Jr.


pgp5PnqSnog3w.pgp
Description: OpenPGP digital signature

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread Geertjan Wielenga 
I don't think there's a need to point to Wikipedias about what a software
release cycle is, do you? :-) The problem we're trying to solve is how to
name voting candidates for the Apache process whereby the initial
candidates for release tend to, especially in a large project like
NetBeans, get rejected and then new voting candidates need to be created
with clearly distinguished names.

Thanks,

Gj


On Fri, Oct 12, 2018 at 8:40 PM William L. Thomson Jr. 
wrote:

> On Fri, 12 Oct 2018 20:31:53 +0200
> Geertjan Wielenga  wrote:
>
> > No one imposed anything. No, contacting mentors and discussing with
> > individual people off-thread is not how Apache projects work.
> >
> > We have a long history in NetBeans outside Apache where we used the
> > term 'release candidate' to mean something very different to how it
> > is used in Apache, i.e., an overloading of terms. This was a way to
> > resolve it suggested by our mentors.
>
> That makes a bit more sense then. You did say in a previous post that
> it came from mentors. I did not understand it was advised by mentors as
> means to continue how Netbeans releases were handled before the move to
> Apache. Or some compromise.
>
> > And, you're not subscribed to this mailing lisy, I keep needing to
> > moderate you, I don't know why. But when you're not seeing your
> > e-mails here, it means I'm not on-line to moderate them.
>
> I was using wrong email. I have an email address specific for posting
> to lists I was not using. Thus receiving but sending under the wrong
> one. Very sorry!!! Thanks for forwarding on those posts!
>
> > I apologize for no one responding to those previous e-mails -- I
> > skipped over them because I think the right approach here in an
> > Apache project is to start a new thread with [PROPOSAL] or [DISCUSS]
> > or something like that, i.e., what you're asking for is actually a
> > new tagging strategy, rather than for a tag to be created with no
> > suffix for a specific release.
>
> I have asked for both, either a change to the current strategy. Or a
> simple duplicate tag. Which I felt was a compromise to satisfy all.
>
> > I also don't understand the entire context -- and having everything
> > hidden in e-mails doesn't help either. For example, Laszlo created
> > this, if you were to create something similar we'd all have a better
> > idea what we're talking about:
>
>  I can see about creating a wiki page to cover the tagging of Netbeans.
>  Not sure if that will help or not. I just assumed tagging software and
>  the various suffixes were well known. I am just asking for things to
>  be standardize.
>
> This pretty much covers it all
> https://en.wikipedia.org/wiki/Software_release_life_cycle
>
> The diagram enough should be suffice
>
> https://en.wikipedia.org/wiki/Software_release_life_cycle#/media/File:Software_dev2.svg
>
> --
> William L. Thomson Jr.
>

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread William L. Thomson Jr. 
On Fri, 12 Oct 2018 20:47:23 +0200
Geertjan Wielenga  wrote:

> I don't think there's a need to point to Wikipedias about what a
> software release cycle is, do you? :-)

I was just trying to express any wiki  page I would create on netbeans
tagging would follow that format _dev, _alpha, _beta, _rc. It would be
redundant like providing a link to that page :)

Or like others I have provided say from Gentoo. The ebuild file format,
maps almost directly to a given version. Which is where I have to keep
being creative for Netbeans.
https://devmanual.gentoo.org/ebuild-writing/file-format/index.html#file-naming-rules

This is nasty! If its 9.0 -> 9.0-vc3, if its 10.0_rc1 -> 10.0-vc1
https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/eclass/java-netbeans.eclass#L26

> The problem we're trying to  solve is how to name voting candidates
> for the Apache process whereby the initial candidates for release
> tend to, especially in a large project like NetBeans, get rejected
> and then new voting candidates need to be created with clearly
> distinguished names.

It seems all other Apache projects use -rc for that. If your voting,
tag it -rc*, if that vote fails. Then increment the number of the -rc.

To me it seems pretty simple and straight forward. Not sure why its
such a problem that needs discussing and solving. Even Apache's own
documentation says that RCs should be voted on.

Release Candidate
A source package and other accompanying artifacts to be inspected
and voted on in order to release.
https://www.apache.org/foundation/glossary.html#ReleaseCandidate


-- 
William L. Thomson Jr.


pgpLAbTWTiUAN.pgp
Description: OpenPGP digital signature

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread Geertjan Wielenga 
You already do know the reason why. I told you already -- in the NetBeans
ecosystem, a 'release candidate' is something different to what it is in
Apache. I can explain it all, but there's no point -- we didn't want to
confuse things and we were confused ourselves, since again, all of this is
new to us. And so we were using the 'release candidate' term in a different
way that it's used in Apache. If we can do it better or help or tweak
things, let's do it. Typically when something seems 'simple and straight
forward', it's not simple and straightforward at all.

Gj


On Fri, Oct 12, 2018 at 9:00 PM William L. Thomson Jr. 
wrote:

> On Fri, 12 Oct 2018 20:47:23 +0200
> Geertjan Wielenga  wrote:
>
> > I don't think there's a need to point to Wikipedias about what a
> > software release cycle is, do you? :-)
>
> I was just trying to express any wiki  page I would create on netbeans
> tagging would follow that format _dev, _alpha, _beta, _rc. It would be
> redundant like providing a link to that page :)
>
> Or like others I have provided say from Gentoo. The ebuild file format,
> maps almost directly to a given version. Which is where I have to keep
> being creative for Netbeans.
>
> https://devmanual.gentoo.org/ebuild-writing/file-format/index.html#file-naming-rules
>
> This is nasty! If its 9.0 -> 9.0-vc3, if its 10.0_rc1 -> 10.0-vc1
>
> https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/eclass/java-netbeans.eclass#L26
>
> > The problem we're trying to  solve is how to name voting candidates
> > for the Apache process whereby the initial candidates for release
> > tend to, especially in a large project like NetBeans, get rejected
> > and then new voting candidates need to be created with clearly
> > distinguished names.
>
> It seems all other Apache projects use -rc for that. If your voting,
> tag it -rc*, if that vote fails. Then increment the number of the -rc.
>
> To me it seems pretty simple and straight forward. Not sure why its
> such a problem that needs discussing and solving. Even Apache's own
> documentation says that RCs should be voted on.
>
> Release Candidate
> A source package and other accompanying artifacts to be inspected
> and voted on in order to release.
> https://www.apache.org/foundation/glossary.html#ReleaseCandidate
>
>
> --
> William L. Thomson Jr.
>

NETBEANS-1359

2018-10-12 Thread Glenn Holmer 
I filed issue 1359 (self-profiling hangs when stopped under JDK 11):

https://issues.apache.org/jira/browse/NETBEANS-1359

and I wonder if someone could help me figure it out. I traced it by
running NetBeans under the debugger:

SelfSamplerAction.actionPerformed() creates an
org.netbeans.modules.sampler.InternalSampler when self-profiling is
started, which creates a SamplesOutputStream.

When self-profiling is stopped, Sampler.stop() gets called (superclass
method), which calls SamplesOutputStream.close(). This calls
writeToStream() on each sample, which fails as soon as toCompositeData()
is called (line 178 in SamplesOutputStream).

Sampler.java doesn't catch the resulting exception (line 239), so the
snapshot save hangs.

Some googling brought me to this issue, which has a similar stacktrace:

https://issues.apache.org/jira/browse/NETBEANS-882

but I'm over my head at this point. Does anyone understand what's going
on with toCompositeData()?

1359 has a repro case, does that help?

-- 
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."

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

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: JIRA question

2018-10-12 Thread Glenn Holmer 
On 10/07/2018 06:54 PM, Glenn Holmer wrote:
> What does it mean when you try to attach a file (e.g. a stack trace) to
> an issue and get the message "JIRA could not attach the file as there
> was a missing token. Please try attaching the file again"? I was logged
> in to JIRA when I saw this.

Never mind, it worked just now.

-- 
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."

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

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread John Yeary 
+1


John Yeary

*NetBeans Dream Team*

*Founder Greenville Java Users GroupJava Users Groups Community Leader*


  
  





"Far better it is to dare mighty things, to win glorious triumphs, even
though checkered by failure, than to take rank with those poor spirits who
neither enjoy much nor suffer much, because they live in the gray twilight
that knows not victory nor defeat."
-- Theodore Roosevelt


On Fri, Oct 12, 2018 at 1:46 PM William L. Thomson Jr. 
wrote:

> On Wed, 3 Oct 2018 07:14:58 +0200
> Geertjan Wielenga  wrote:
>
> > No
>
> YES
>
> > the Apache terminology is voting candidate.
>
> Just because Apache terminology is voting candidate. That does not mean
> it should be tagged as such. I package quite a few Apache projects.
> NONE use this crazy format of -vc*. Most Apache release are voted on.
>
> Please stick with common stuff, dev, alpha, beta, pre. For releases
> there should be NO additional suffix.
>
> > On Wed, Oct 3, 2018 at 7:06 AM László Kishalmi
> >  wrote:
> >
> > > I meant: I'm not sure that we need to vote on this. It's more like
> > > a beta. Shouldn't we have called it beta at first? Just for the
> > > further release processes...
>
> Yes it should be a -beta or -pre, or something standard...
>
> Examples of other Apache release that were voted on and released
> without crazy tags
>
> You can see Votes
> https://www.mail-archive.com/dev@maven.apache.org/
>
> No crazy -vc tags
> https://github.com/apache/maven-resolver/releases
> https://github.com/apache/maven/releases
>
> Some more apache projects
> https://github.com/apache/tomcat/releases
> https://github.com/apache/ant/releases
> https://github.com/apache/commons-pool/releases
> https://github.com/apache/commons-logging/releases
>
> I have never seen any Apache project use -vc for tagging a vote
> candidate. They may exist, but the first time I recall seeing this was
> with Apache Netbeans. Can anyone find another Apache project that has
> -vc tags? If not then why is Netbeans doing this?
>
> This is what I had to do for 9.0. Nasty hidden change of version.
>
> https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/eclass/java-netbeans.eclass#L17
>
> I have to do something similar for 10.0-vc1. Which I also have to add
> some other prefix, as I cannot use 10.0 -> 10.0-vc1 like I do for 9.0.
> As 10 is not fully released, there maybe another 10.0-vc*
>
> On github seems like 9.0 was never released What is the difference
> between 9.0-vc* and 10.0-vc* ? Which one the release?  Which one is
> just a voting candidate?
> https://github.com/apache/incubator-netbeans/releases
>
> If you must continue on with -vc tags. Please create another non -vc
> tag for the actual release. You can have more than one tag for a given
> commit. But really the -vc stuff is just confusing. It seems only
> Netbeans is using this odd format. It is not standard.
>
> --
> William L. Thomson Jr.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread Laszlo Kishalmi 

I think there is nothing wrong with this additional tag. It makes sense.

The 9.0 tag has been created and uploaded to the GitHub repository.


On 10/12/2018 11:22 AM, William L. Thomson Jr. wrote:

On Fri, 12 Oct 2018 20:07:45 +0200
Geertjan Wielenga  wrote:


Just bear in mind that we're new to all this. Can you tone down your
exasperation and try to bear that in mind?

Sorry, but I have repeatedly brought up this issue.
https://lists.apache.org/thread.html/d31294f296a99d7379ca4ca78a8a5ec33bd12f6a7e365b2e67182a05@%3Cdev.netbeans.apache.org%3E
https://lists.apache.org/thread.html/1c3a1af37c49baeb1e29664999f826d298316fa3eaa97656ac46d1cf@%3Cdev.netbeans.apache.org%3E


I think we should definitely revisit this, if it's causing problems
and confusion, we could start a new thread to discuss this.

I have... It feel on deaf ears
https://lists.apache.org/thread.html/2aedd00af7ae24b8b4c23f62afeacbaeeb9ea22145252b1d2638df3c@%3Cdev.netbeans.apache.org%3E

That was a simple request for a duplicate tag... Can you see where the
frustration comes from ~6 months of trying to correct tags. I can make
another to discuss the tagging. I feel we have covered this several
times already though


Also, can you join this mailing list, right now I have to moderate
each mail you send, and I'm not always on-line, so sometimes it's
going to be even more exasperating to you, to see your messages not
appearing here.

I have repeatedly... I get emails which means I should be subscribed. I
will subscribe again. No clue how I am getting list posts without being
subscribed :)

I have been removed in the past automatically due to bounced emails.
Though that does not happen on other lists. Occasionally I get a warning
usually from JClouds mailing list. Never from Maven, or Tomcat when I
was on Tomcat dev list.





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

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread Geertjan Wielenga 
Well, nice, and it makes sense, and if this helps to solve this, excellent
too.

We could/should revisit the -vc naming, I think -- maybe for the next
release, and try to follow the Apache way of doing this, to avoid this
confusion.

Gj



On Fri, Oct 12, 2018 at 9:43 PM Laszlo Kishalmi 
wrote:

> I think there is nothing wrong with this additional tag. It makes sense.
>
> The 9.0 tag has been created and uploaded to the GitHub repository.
>
>
> On 10/12/2018 11:22 AM, William L. Thomson Jr. wrote:
> > On Fri, 12 Oct 2018 20:07:45 +0200
> > Geertjan Wielenga  wrote:
> >
> >> Just bear in mind that we're new to all this. Can you tone down your
> >> exasperation and try to bear that in mind?
> > Sorry, but I have repeatedly brought up this issue.
> >
> https://lists.apache.org/thread.html/d31294f296a99d7379ca4ca78a8a5ec33bd12f6a7e365b2e67182a05@%3Cdev.netbeans.apache.org%3E
> >
> https://lists.apache.org/thread.html/1c3a1af37c49baeb1e29664999f826d298316fa3eaa97656ac46d1cf@%3Cdev.netbeans.apache.org%3E
> >
> >> I think we should definitely revisit this, if it's causing problems
> >> and confusion, we could start a new thread to discuss this.
> > I have... It feel on deaf ears
> >
> https://lists.apache.org/thread.html/2aedd00af7ae24b8b4c23f62afeacbaeeb9ea22145252b1d2638df3c@%3Cdev.netbeans.apache.org%3E
> >
> > That was a simple request for a duplicate tag... Can you see where the
> > frustration comes from ~6 months of trying to correct tags. I can make
> > another to discuss the tagging. I feel we have covered this several
> > times already though
> >
> >> Also, can you join this mailing list, right now I have to moderate
> >> each mail you send, and I'm not always on-line, so sometimes it's
> >> going to be even more exasperating to you, to see your messages not
> >> appearing here.
> > I have repeatedly... I get emails which means I should be subscribed. I
> > will subscribe again. No clue how I am getting list posts without being
> > subscribed :)
> >
> > I have been removed in the past automatically due to bounced emails.
> > Though that does not happen on other lists. Occasionally I get a warning
> > usually from JClouds mailing list. Never from Maven, or Tomcat when I
> > was on Tomcat dev list.
> >
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: [VOTE] Release Apache Netbeans 10.0 (incubating) [vote candidate 1]

2018-10-12 Thread William L. Thomson Jr. 
On Fri, 12 Oct 2018 12:43:05 -0700
Laszlo Kishalmi  wrote:

> I think there is nothing wrong with this additional tag. It makes
> sense.
> 
> The 9.0 tag has been created and uploaded to the GitHub repository.

Thank you very much

-- 
William L. Thomson Jr.


pgpZFce2mw_8E.pgp
Description: OpenPGP digital signature