I'm working on a large codebase that I've inherited. I'm going to be
submitting it to an open-source team that has certain standards I have
to adopt. One of them is javadoc. Very few of my existing classes have
javadoc tags, but the build in the new project requires them. When I
run the Mav
I was attempting to search for available artifacts in the "add artifact"
dialog. It was able to find common third-party libraries, but when I
entered common search strings for "custom" libraries, even though those
artifacts are deployed in the repositories defined in my ~/.m2/settings
(they've
I'm having trouble understanding how to control what repos go into the
"Project Repositories" list in the "Maven Repositories" view. I have
three Eclipse distributions and workspaces, all using the same
".m2/settings.xml" file, and all having similar projects and plugins
loaded. The list of r
I have an Eclipse plugin codebase built with Tycho. The parent pom that
I get from a maven repo has the checkstyle config, including the custom
ruleset required the project.
How exactly do I get m2e in Eclipse to use the same checkstyle config
used in the build? I saw Eclipse install a m2e c
I've always been under the impression that Eclipse Maven projects should
write their classes (from Eclipse) into the default "bin" and not share
the same output folder as the command line build, using "target".
However, I've never had definite information about this. Are there
specific issues
For a while I've been struggling with an issue where I see the search
facility in the "Add" dialog offering some artifacts that are "jar"
artifacts, and some that are "bundle" artifacts. I know the basic
difference between them. The funny thing is, I believe that these
artifacts are all struc
ing the user from creating a
situation that will definitely fail, perhaps not so much.
Am 25.05.2016 um 19:38 schrieb David M. Karr :
For a while I've been struggling with an issue where I see the search facility in the "Add" dialog offering some
artifacts that are "ja
type is usually the extension
(according to maven docs) m2e chooses it.
On 25 May 2016 at 17:37, David M. Karr <mailto:davidmichaelk...@gmail.com>> wrote:
On 05/25/2016 10:54 AM, Konrad Windszus wrote:
Type is actually determined only by the packaging of the
re
I'm looking at a project with a POM file, with a "repositories" section
like this:
---
opendaylight-release
opendaylight-release
https://nexus.opendaylight.org/content/repositories/opendaylight.release/
opendaylight-snapshot
openda
s
list in that view?
Eric
On Jun 1, 2016 7:13 PM, "David M. Karr" <mailto:davidmichaelk...@gmail.com>> wrote:
I'm looking at a project with a POM file, with a "repositories"
section like this:
---
different.
Rereading it, I am also confused by the results that you see.
Eric
On Wed, Jun 1, 2016 at 8:50 PM, David M. Karr
mailto:davidmichaelk...@gmail.com>>
wrote:
On 06/01/2016 04:35 PM, Eric B wrote:
You also have to consider any inherited
When adding a dependency, the label in the "Add" dialog says "Enter
groupId, artifactId or sha1 prefix or pattern(*)". I've gone through
this dialog billions of times and never really read that label. What
exactly is a "sha1 prefix" in this context?
___
I've always been a bit confused about repository indexing. I normally
work on a Linux laptop, and it's been working well enough there for a
while. This has been using Mars.2.
Today I've been trying to get a project set up on my Win7 work laptop,
using the latest Neon.
I'm working with two
13 matches
Mail list logo
