Hi,
based on the information I see currently the "default" issue types are
the following which does not contain "Question" and others...
* Bug
* Improvement
* New Feature
* Task
* Test
* Wish
* Sub-Task
Kind regards
Karl Heinz Marbaise
On 18/08/17 21:14, Michael Osipov wrote:
Am 2017-08-18
B too
Le ven. 18 août 2017 à 21:14, Michael Osipov a écrit :
> Am 2017-08-18 um 20:59 schrieb Robert Scholte:
> > I like the idea of having our own scheme for all projects.
> > That will also give the option to remove types like "Question"; now once
> > used we're always
Am 2017-08-18 um 20:59 schrieb Robert Scholte:
I like the idea of having our own scheme for all projects.
That will also give the option to remove types like "Question"; now once
used we're always asking them to use other ways to get an answer. But it
is an option, so it is kind of valid to
I like the idea of having our own scheme for all projects.
That will also give the option to remove types like "Question"; now once
used we're always asking them to use other ways to get an answer. But it
is an option, so it is kind of valid to use it.
thanks,
Robert
On Fri, 18 Aug 2017
Hi to all,
I have realized that in MASSEMBLY it is possible to define an issue Type
"Dependency Upgrade" which is very feasible for our projects...
So I have asked INFRA[1] if we could have that for our other JIRA
projects as wellSo the now we can decide between three options:
A)
Github user asfgit closed the pull request at:
https://github.com/apache/maven-shared/pull/24
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user asfgit closed the pull request at:
https://github.com/apache/maven-plugins/pull/125
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Tibor,
I have tested with java.se.ee too and it works fine for me too.
I hope we can release 2.21 soon
thank you very much again
Enrico
2017-08-18 9:25 GMT+02:00 Tibor Digana :
> Hi Enrico,
>
> Using "--add-modules java.se.ee" works fine:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
GitHub user oleg-nenashev opened a pull request:
https://github.com/apache/maven-plugins/pull/125
[MJARSIGNER-53] - Add support of the "certchain" option in the "sign" mojo
This adds a new optional parameter for "certchain". If the maintainers are
fine with the approach, I will add
GitHub user oleg-nenashev opened a pull request:
https://github.com/apache/maven-shared/pull/24
[MJARSIGNER-53] - Add support of the "certchain" parameter in JarSigner
sign operation
This adds a new optional parameter for "certchain". If the maintainers are
fine with the approach,
Hi Enrico,
Using "--add-modules java.se.ee" works fine:
*mvn install "-Djdk.home=e:\Program
Files\Java\jdk9"--- T E
S T S---Concurrency
config is parallel='none',
11 matches
Mail list logo